[Top][All Lists]

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

Re: Referring to revisions in the git future.

From: Eric S. Raymond
Subject: Re: Referring to revisions in the git future.
Date: Wed, 29 Oct 2014 05:52:48 -0400
User-agent: Mutt/1.5.21 (2010-09-15)

David Kastrup <address@hidden>:
> Just use the SHA1.

Please *don't* use the SHA1.  It's an opaque blob, not portable to any 
future VCS we may need to move to someday.  It is better, and more human 
friendly, to refer to commits by their summary line, or by committer 
and date.

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. We're no longer in CVS-land, commits are cheap,
make them fine-grained.  

Git tools (and Mercurial tools, and it is a safe bet future DVCS tools
as well) like there to be a short, self-contained summary line
beginning the change comment.  This makes the history easier to read
in tools like gitk and hg view. 

If you can't express your intention in a short summary line, you should
break up the change into smaller commits until you can.
                <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>

reply via email to

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