Re: inaccurate commit message message?

From: Sverre Rabbelier <srabbelier@gmail.com>
Date: Sep 4, 2010, 21:55 UTC
Message-ID: <AANLkTinGNss5siAjpic07OB036y8K0kvBjSj=unDhQWs@mail.gmail.com>
In-Reply-To: <AANLkTinbq8z-ygVUWPRq9PA95-+8O8SwOJCLkfMKCg9T@mail.gmail.com>

Heya,

On Sat, Sep 4, 2010 at 16:37, Ramana Kumar <ramana.kumar@gmail.com> wrote:

> The commit message message says "Lines starting with '#' will be
> ignored", but fails to say "Lines below this message will be ignored,
> even if they don't start with '#'".

Because they're not. Only those starting with # are ignored.

> If the second sentence is true, I think it (or something equivalent)
> should be said, especially because of the relevance during commit
> --verbose.

It is not true.

> In fact the documentation for commit --verbose explicitly says to note
> that the diff lines won't start with '#'s, as if warning people that
> those lines might show up in the commit message.
> Yet they do not seem to show up... (and I don't think they should)

Ah, you are apparently talking about 'git commit --verbose'. It works a little different there, all lines starting with # are ignored, as well as everything in and after the diff.

-- 
Cheers,

Sverre Rabbelier