Re: [FAQ?] Rationale for git's way to manage the index

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: May 9, 2007, 13:57 UTC
Message-ID: <Pine.LNX.4.64.0705091513360.4167@racer.site>
In-Reply-To: <20070509125225.GP4489@pasky.or.cz>

Hi,

On Wed, 9 May 2007, Petr Baudis wrote:

Show 11 quoted lines

> On Sun, May 06, 2007 at 07:43:31PM CEST, Junio C Hamano wrote:
> > A single liner "-m" is handy for "Oops, typofix in foo.c" kind
> > of commit, but in such a case you literally would be changing
> > only the typofix and won't have "edit foo.c; git add foo.c; edit
> > foo.c; git commit" sequence anyway.
> 
> I don't get this argument - I frequently write quite long descriptions
> inside the -m argument(s), since I just find it more convenient than
> having to edit it in an editor, for various reasons. So there is really
> no reason why the "-m is only for short single-liner commit messages"
> hypothesis could hold true.

:-) You yourself provided a reason in another reply: typos.

Another reason is that you can see how the end result will look like in an editor. For example, you'll have a hard time making sure in the command line that the lines are no longer than 76 characters.

Ciao, Dscho