[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Referring to revisions in the git future.

From: Stefan Monnier
Subject: Re: Referring to revisions in the git future.
Date: Wed, 29 Oct 2014 08:35:33 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)

> About summary lines, a reminder: Please don't write the traditional
> GNUish run-on change comment with a semi-infinite number of bulleted
> items in it any more.

That's your opinion, but the convention we still use here (and don't
just recommend but *request* people to follow) is the GNU ChangeLog format.

> We're no longer in CVS-land, commits are cheap,

Don't know yet about Git, but I can assure you that in Bzr-land, commits
are not cheap (things like "bzr merge", "bzr annotate" and many others
have time complexities that depend on the number of commits).

> make them fine-grained.

Fine-grained or not is irrelevant.  What they should be is logical/coherent.
Your recent 20 or so single-line commits which all have the same summary
line is the perfect example of what should *not* be done.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]