I'm not "wrong", I know git is behaving as it was specified to behave.
I just think the other way would be better, and suggesting the specification could be changed. In which use cases there are comment lines mixed with the commit message? On Fri, May 3, 2013 at 3:20 PM, Konstantin Khomoutov <flatw...@users.sourceforge.net> wrote: > On Fri, 3 May 2013 08:00:32 -0700 (PDT) > bart9h <rodolfo.bor...@gmail.com> wrote: > >> When you edit the commit message, it comes with a bunch of comments >> at the end of the file that will be removed automatically later. >> >> I thought it should remove just the consecutive lines starting with # >> at the end of the file, not lines starting with # inside the message, >> like: >> >> summary of the changes >> >> This is the longer explanation, and >> # this line here should not be removed. >> Am I wrong? > > As Dale pointed out, you're wrong. > But it seems you could pass the "--cleanup=whitespace" command-line > option to `git commit` to make it not touch the comment lines. > You will have to manually remove them though. Or play with > the commit.template configuration option. Or may be with a hook which > is called to precompose the commit message (I can't recall its exact > name at the moment). -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
