> From: Rodolfo <rodolfo.bor...@gmail.com>
>
> 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.
Be aware that there is a language difficulty here: The particular
verb forms that you used in your original message imply that you
believed in the past that Git would remove just the lines starting
with # at the end of the file:
> >> I thought it should remove just the consecutive lines starting with #
"I thought" implies that you thought this in the past, but since then
you changed your belief. This suggests that your belief was changed
by seeing that Git did not behave as you believed it would. (In this
meaning, the "should" should be omitted, and appears to the reader
(i.e., me) to be a simple error.)
Your query
> >> Am I wrong?
suggests that you are discussing a matter of fact.
If you want to express an opinion as to how Git should behave, you
would use this verb form:
I think it should remove ...
In this case, a query asking if we agree or disagree with this opinion
would be
Do you agree?
(The meanings of the various English verb forms are quite complicated
and irregular. But you are quite fluent in English, so we assumed
that you were using them in an exact manner.)
--
And I do agree that Git should only remove the lines starting with #
at the end of the file. (Subversion uses a similar convention.)
> 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.
