On Tue, 7 May 2013 15:19:22 -0300
Rodolfo <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).
> 
> I'm not "wrong", I know git is behaving as it was specified to behave.

Don't be offended, please.  You asked if you were wrong and I answered
that yes, you did.  That wasn't to underline your "wrongness" or
something like that, just answering the question.

> I just think the other way would be better, and suggesting the
> specification could be changed.

I, too, think that removing all the comment lines might be good for
scripts but is supposedly not so good for humans.

> In which use cases there are comment lines mixed with the commit
> message?

I, for one, do not know.  I can make a wild guess: in certain
situations a commit message might end up being composed out of several
templates, each inserting its own comments.  This is a pure
speculation, though.

Note that from following the main Git list for some time I gathered
that not every Git feature (or misfeature) is there for a reason --
quite some of them are there just because they got implemented in a way
which seemed reasonable at the moment and only extensive usage proved
the initial premises to be wrong.  In this venue I might recall the
"--set-upstream" command-line option to `git branch` (which no single
human being seemed to use correctly on the first try) and the default
value of the "push.default" configuration option (which is hardly
suitable for beginners).

So I think you might consider asking a question on the main Git list [1]
to hear the opinion of Git developers.

1. http://vger.kernel.org/vger-lists.html#git

-- 
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.


Reply via email to