From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Referring to revisions in the git future. Date: Wed, 29 Oct 2014 12:00:18 +0100 Organization: Organization?!? Message-ID: <87y4rz9m4d.fsf@fencepost.gnu.org> References: <20141028223312.GB6630@acm.acm> <87fve7b6p7.fsf@fencepost.gnu.org> <20141029095248.GA14601@thyrsus.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1414580473 11289 80.91.229.3 (29 Oct 2014 11:01:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 29 Oct 2014 11:01:13 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 29 12:01:06 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XjQzy-0004lc-LT for ged-emacs-devel@m.gmane.org; Wed, 29 Oct 2014 12:01:06 +0100 Original-Received: from localhost ([::1]:44991 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XjQzy-0000vy-82 for ged-emacs-devel@m.gmane.org; Wed, 29 Oct 2014 07:01:06 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54720) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XjQze-0000vk-Ex for emacs-devel@gnu.org; Wed, 29 Oct 2014 07:00:51 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XjQzV-0006Ie-9o for emacs-devel@gnu.org; Wed, 29 Oct 2014 07:00:42 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:50027) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XjQzU-0006Ia-KY for emacs-devel@gnu.org; Wed, 29 Oct 2014 07:00:37 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XjQzN-0004NR-Vw for emacs-devel@gnu.org; Wed, 29 Oct 2014 12:00:30 +0100 Original-Received: from x2f49ee0.dyn.telefonica.de ([2.244.158.224]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 29 Oct 2014 12:00:29 +0100 Original-Received: from dak by x2f49ee0.dyn.telefonica.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 29 Oct 2014 12:00:29 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 48 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: x2f49ee0.dyn.telefonica.de X-Face: 2FEFf>]>q>2iw=B6, xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN; i"; /yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) Cancel-Lock: sha1:MxZtQudf0dQw+eNEMOD9PFTxtTs= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:175971 Archived-At: "Eric S. Raymond" writes: > David Kastrup : >> 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. Shrug. Not if the human actually wants to use it for any purpose. It's fine to be more explicit, like commit 0c59175f0867663196e77061786dc07708d69894 Author: David Kastrup Date: Wed Jan 1 12:47:42 2014 +0100 Some parser work, mostly unconvincing But in the end, the one thing that is actually definitive is the commit id. And I don't see it as either more or less useful than a revision number. You don't want to type in either by hand, but at least the commit id is reasonably safe against typos, given enough digits. > 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. Commits are awfully expensive since they should contain the ChangeLog entries corresponding to each commit. With regard to ChangeLog entries, we are still quite in CVS-land (though CVS commits only allowed one file at a time, making it even worse to keep track of the corresponding ChangeLog entry). One thing that we really used ChangeLog for is distinguishing between committer and author of a change, and we needed to keep track of the latter for copyright and attribution reasons. Fortunately, Git keeps track of both. At any rate, as long as ChangeLog entries are here to stay (and that's a different discussion we had a few times), "commits are cheap" is not matching reality. Each commit tends to come with its own manual conflict resolution for ChangeLog. -- David Kastrup