DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc
	:subject:references:date:in-reply-to:message-id:mime-version
	:content-type; q=dns; s=sasl; b=rKwYJvK9ii1geD/oA7L8cHNz7l8XxgRI
	0jvVIBugM1YXIwe7Prp5rMKX9+R3GNfSGLSCT4/4k08xdahV1B/iff5AqCQOE3EX
	oKo2SjKu4fSo8ZgPVxP8T9cWQNPBIgEYNr/TOfVeUmoIk608QrF5jq17zqCGp6px
	uD6lPN5r3Hk=
From:	Junio C Hamano <gitster@pobox.com>
To:	Jon Forrest <nobozo@gmail.com>
Cc:	Rodrigo Campos <rodrigo@sdfg.com.ar>, git@vger.kernel.org
Subject: Re: [RFC] A Change to Commit IDs Too Ridiculous to Consider?
References: <nn30dv$5sn$1@ger.gmane.org> <20160724185132.GN25141@sdfg.com.ar>
	<c0af7511-a5d5-29bb-d279-66b6c3e0519c@gmail.com>
Date:	Mon, 25 Jul 2016 08:03:46 -0700
In-Reply-To: <c0af7511-a5d5-29bb-d279-66b6c3e0519c@gmail.com> (Jon Forrest's
	message of "Sun, 24 Jul 2016 12:57:50 -0700")
Message-ID: <xmqq1t2h92ul.fsf@gitster.mtv.corp.google.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Sender:	git-owner@vger.kernel.org
Precedence: bulk

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.