Hi, I just looked how you solved that and wanted to start a discussion but you've swooped in first, find. ;-) > I think it its current form that is not a bugfix. The user may want to > prepend a custom message and may want to replace the original message > with a custom one, and I would not consider either of them as "buggy". Well, when I do -m <msg>, I expect that my commit message is exactly <msg>, and not <msg> with appended stuff. Of course, it doesn't matter what I expect, but I think what the documentation says matters. This is (in "master" and in "builtin-merge" of vmiklos.git): -m <msg>:: The commit message to be used for the merge commit (in case it is created). The `git-fmt-merge-msg` script can be used to give a good default for automated `git-merge` invocations. So it is not mentioned that a standard message is appended, and thus the original behavior is somehow "buggy" :) Regards, Stephan -- Stephan Beyer <s-beyer@xxxxxxx>, PGP 0x6EDDD207FCC5040F
Attachment:
signature.asc
Description: Digital signature
