Signal conflict on merging metadata-differing patches

[Eugeniu Rosca]

Dear Git community,

Due to high inflow of patches which Linux maintainers carry on their
shoulders and due to occasionally intricate relationships between
consecutive revisions of the same series, it may [1] happen that two
distinct revisions of the same patch (differing only/mostly in
metadata, e.g. Author's time-stamp and commit description) may end up
being merged on the same branch, without git to complain about that.

Is there any "git merge" flag available off-the-shelf which (if used)
would signal such situations?

[1] https://patchwork.kernel.org/patch/11135107/#23007101

-- 
Best Regards,
Eugeniu