Re: [RFC] A Change to Commit IDs Too Ridiculous to Consider?

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 25, 2016, 15:03 UTC
Message-ID: <xmqq1t2h92ul.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <c0af7511-a5d5-29bb-d279-66b6c3e0519c@gmail.com>

Jon Forrest <nobozo@gmail.com> writes:

> Sure. Take a look at the 2nd or 3rd chapter of Pro Git Reedited, 2nd
> Edition (or just Pro Git 2nd Edition - it doesn't matter). You see
> lots of output showing 'git commit' commands and the commit IDs that
> result. I suspect you'd see the same in almost any book about Git.

I would think that the early-stage learners are better served that it is the norm, not anything strange, that the commit object name would be different when you do two identical sequence from scratch. Forcing them to know GIT_*_DATE variables, just to give them an impression as if setting of them is part of any normal workflow (or more importantly, stable commit IDs made by different people at different times is something expected), is doing them double disservice, IMHO.