This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Moving to git


Jonathan Wakely <jwakely.gcc@gmail.com>:
> On 24 August 2015 at 09:17, Jakub Jelinek wrote:
> > The revision ids are also useful for bugzilla, r123456
> > links in text pointing to http://gcc.gnu.org/r123456 is significantly
> > shorter
> 
> The first six characters of the sha1 is usually enough to
> unambiguously identify a commit, so we could easily have
> https://gcc.gnu.org/git/f00baa or something similar, if we don't use
> git-notes to add a revision to the commits.

I recommend *against* using hashes to identify commits.  Here's what I said
about it in the NTPsec developers guidelines.

=== How to refer to previous commits ===

The best (most human-friendly) way to reference a commit is by quoting its
summary line.  If you need to disambiguate, give its date and author.

The worst way is to quote its git hash, because humans are not good at
keeping random strings of hex digits in working memory.  Besides, hashes
will break if the history is ever moved to another VCS or the repository
has to be surgically altered.
-- 
		<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]