From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Joshua Judson Rosen Newsgroups: gmane.emacs.devel Subject: Policy on referencing/abbreviating git commit-IDs, going forward? (was: Can anyone correct the Bazaar reference "revno:111954.1.97"?) Date: Sun, 02 Mar 2014 15:01:50 -0500 Message-ID: <87r46kv07l.fsf_-_@slice.rozzin.com> References: <20140301171337.53CC638073E@snark.thyrsus.com> <8338j1vkta.fsf@gnu.org> <87fvn17gbc.fsf@slice.rozzin.com> <20140301220207.GC19461@thyrsus.com> <87eh2l5kif.fsf@slice.rozzin.com> <83iorwtrzd.fsf@gnu.org> <871tykihi1.fsf@igel.home> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1393790519 4900 80.91.229.3 (2 Mar 2014 20:01:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 2 Mar 2014 20:01:59 +0000 (UTC) Cc: esr@thyrsus.com, handa@gnu.org, Eli Zaretskii , emacs-devel@gnu.org To: Andreas Schwab Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Mar 02 21:02:07 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 1WKCaN-0008GI-Nf for ged-emacs-devel@m.gmane.org; Sun, 02 Mar 2014 21:02:07 +0100 Original-Received: from localhost ([::1]:36505 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WKCaN-0008Rw-1F for ged-emacs-devel@m.gmane.org; Sun, 02 Mar 2014 15:02:07 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51890) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WKCaG-0008RT-W3 for emacs-devel@gnu.org; Sun, 02 Mar 2014 15:02:05 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WKCaC-0001PP-Jf for emacs-devel@gnu.org; Sun, 02 Mar 2014 15:02:00 -0500 Original-Received: from 209-20-69-211.slicehost.net ([209.20.69.211]:49132 helo=slice.rozzin.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WKCa7-0001OS-CL; Sun, 02 Mar 2014 15:01:51 -0500 Original-Received: by slice.rozzin.com (Postfix, from userid 1000) id 694B7C8622; Sun, 2 Mar 2014 15:01:50 -0500 (EST) In-Reply-To: <871tykihi1.fsf@igel.home> (Andreas Schwab's message of "Sun, 02 Mar 2014 19:26:46 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 209.20.69.211 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:170064 Archived-At: Andreas Schwab writes: > > Eli Zaretskii writes: > > > This is bzr, not git, so the diffs aren't the whole story. > > There is no difference between git and bzr wrt. to the DAG. Only the > names they use are different. There is an interesting `bzr vs. git' question here, though--because of the differences in the way revisions are named: when you run into the analogous "I can't tell what this reference is to" problem in git, how will you deal with it? When someone writes a abbreviated git sha1sum into a changelog / commit message because just the first 7 or howevermany hexits was enough to unambiguously identify the referenced commit-object in their development environment at the time when they were committing their change, and then a later commit/merge makes that abbreviation ambiguous, how will you trace out the now-ambiguously- abbreviated commit? e.g.: up through July 29 2012, "7a62fbf" unambiguously identified a commit from October 24 2007; on July 30 2012, "7a62fbf" stopped being unambiguous. -- "'tis an ill wind that blows no minds."