From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Barry Warsaw Newsgroups: gmane.emacs.devel Subject: Re: Referring to revisions in the git future. Date: Wed, 29 Oct 2014 10:52:02 -0400 Organization: Damn Crazy Followers of the Horn Message-ID: <20141029105202.249acb5a@anarchist.wooz.org> References: <20141028223312.GB6630@acm.acm> <20141029004942.GA25241@thyrsus.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/gBNuOG+URVHqYmO32+asG7D"; protocol="application/pgp-signature" X-Trace: ger.gmane.org 1414594401 25643 80.91.229.3 (29 Oct 2014 14:53:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 29 Oct 2014 14:53:21 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 29 15:53:14 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 1XjUcb-0006Or-5q for ged-emacs-devel@m.gmane.org; Wed, 29 Oct 2014 15:53:13 +0100 Original-Received: from localhost ([::1]:46657 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XjUca-0004JO-Sr for ged-emacs-devel@m.gmane.org; Wed, 29 Oct 2014 10:53:12 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54660) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XjUc8-00047Z-Kx for emacs-devel@gnu.org; Wed, 29 Oct 2014 10:52:52 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XjUbx-0006Dg-0E for emacs-devel@gnu.org; Wed, 29 Oct 2014 10:52:44 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:44210) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XjUbw-0006DU-PM for emacs-devel@gnu.org; Wed, 29 Oct 2014 10:52:32 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XjUbl-0005pd-2f for emacs-devel@gnu.org; Wed, 29 Oct 2014 15:52:21 +0100 Original-Received: from mail.wooz.org ([216.15.33.194]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 29 Oct 2014 15:52:21 +0100 Original-Received: from barry by mail.wooz.org with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 29 Oct 2014 15:52:21 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 70 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: mail.wooz.org X-Newsreader: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) 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:176006 Archived-At: --Sig_/gBNuOG+URVHqYmO32+asG7D Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Oct 28, 2014, at 08:49 PM, Eric S. Raymond wrote: >Git does not have such a mapping. This is not the git designers being >perverse; all other DVCSes have the same issue. A true DVCS is >designed for distributed operation in which there is no privileged node >to hand out the monotonically-increasing IDs. This is certainly true in theory, but in practice you almost always have sufficient context for monotonically increasing revision numbers[*] to make sense. For example, bzr has both revision hashes for unique reference, but it also has human friendly revision numbers, which will generally be completely fine to use in practice. When used like this, the context is almost always for = the "trunk" branch in the "master" repository. Yes, of course dvcs, democracy, and all, but I claim that most projects hav= e a canonical place for their source code. If you ask their project leaders "h= ow do I get your code", they will answer with the url to this canonical locati= on. Thus, "your bug is fixed in r19801" has implied context for this url, and t= he master, trunk, line-of-development (or whatever you call it) branch. git really doesn't acknowledge this common development workflow, so it's understandable that it doesn't in anyway support human readable revision id= s. It's also true that in e.g. bzr, if you really had to refer to a unique revision id, you can use the hash. It's just that in polite conversation , it's rarely needed. Cheers, -Barry [*] Although it's true that some bzr merge operations can "mess with" those numbers, it's generally bad practice to use merge in such a way as to cause this to happen. --Sig_/gBNuOG+URVHqYmO32+asG7D Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJUUP8SAAoJEBJutWOnSwa/TzYP/0aMabv1V9DtNsn8pZVanJaP yrYnZBjoyd21NXtL2h5GKd/aynwV7i2pg7DrptrCVP5lNMUk3v5zByWavjPrDo8h zDDpDhZdX+kWTz6Bhi1rOCKn/61p9l9gUZsPb76Q1uVc61MjtKiY/bzqLnIwzAwF ij/B+sltfP0K6zhesOAch1htVUiRUwzRAhiRfZJahcO5wTdVS8j840v3c5sjBRUZ ZPYl+Ehg312T6CXf/OwmW+RMDITa4aesN6seXzgqqcfWgefORVwr+a0qL4h17hoa x/jKx/uGC57/TXbvAwtXfT9G1bITU5htF8EH2plp8VY+aoJWM4pXZxhieHE8I8Vw he1zrDD1Ps5572Xwm5vf67jh9+TcA9795GeLwXcVdRFHT+EEm+2KnnqYfCY0LiDq ZCjhk35lPi/VumUVqvYghVK29pla6XKXLpHQ+Z/Okr6Fs+RloAGmyYUjFjT08uEh py4OU2YTpf1zuTBSzDQFYjJw2lSEs/iTWs6YCUlJkSZczxOtSmBdCf8gw/zhBdej FFDJNSGry5h/UfZBtqLjwGX4a8Bc3NEPxzWO5kYWjGuQI10Hf1vN91yqVHqyg6LI CyIF/92+BWFSyse7wEuqh3+QFYduDeuoSvo4MrPXwv0OYOHb1Kmi602NPPPkS0Bx Lo4wmketzBbuSYjxZVV+ =1DR1 -----END PGP SIGNATURE----- --Sig_/gBNuOG+URVHqYmO32+asG7D--