From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: Git mirrors Date: Fri, 07 Oct 2011 01:50:36 +0200 Message-ID: <874nzliss3.fsf@wanadoo.es> References: <0h62k1hm6a.fsf@fencepost.gnu.org> <878voxiwh6.fsf@wanadoo.es> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: dough.gmane.org 1317945059 17079 80.91.229.12 (6 Oct 2011 23:50:59 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 6 Oct 2011 23:50:59 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 07 01:50:55 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RBxiJ-0003UH-4f for ged-emacs-devel@m.gmane.org; Fri, 07 Oct 2011 01:50:55 +0200 Original-Received: from localhost ([::1]:55688 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RBxiI-0007rl-G7 for ged-emacs-devel@m.gmane.org; Thu, 06 Oct 2011 19:50:54 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:34976) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RBxiG-0007rZ-EL for emacs-devel@gnu.org; Thu, 06 Oct 2011 19:50:53 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RBxiF-0006GP-2r for emacs-devel@gnu.org; Thu, 06 Oct 2011 19:50:52 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:51657) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RBxiE-0006GF-Sq for emacs-devel@gnu.org; Thu, 06 Oct 2011 19:50:51 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1RBxiC-0003SA-HB for emacs-devel@gnu.org; Fri, 07 Oct 2011 01:50:48 +0200 Original-Received: from 175.red-83-45-165.dynamicip.rima-tde.net ([83.45.165.175]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 07 Oct 2011 01:50:48 +0200 Original-Received: from ofv by 175.red-83-45-165.dynamicip.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 07 Oct 2011 01:50:48 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 31 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 175.red-83-45-165.dynamicip.rima-tde.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) Cancel-Lock: sha1:e202PBE7XGwkD5NJFUcCE+3tl+U= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 80.91.229.12 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:144657 Archived-At: Juanma Barranquero writes: > On Fri, Oct 7, 2011 at 00:30, Óscar Fuentes wrote: > >> bzr has something like that, but time ago the people here >> decided that knowing that information is not really useful, so just >> ignore it. > > In some other universe, perhaps. So let's make use of the next wormhole, then. Some stuff, if you have time to skim over unrelated posts: http://search.gmane.org/?query=bzr+revision+id+version&group=gmane.emacs.devel If you are too impatient, peek through this for a quick taste of that strange universe: http://article.gmane.org/gmane.emacs.devel/129532 > In this one, the discussion was not > about where bzr ids are useful, but whether they are so convenient to > use that they should be routinely used when referring to trunk's > revisions in commit logs and ChangeLogs. They are not. Chalk that one > to Bazaar developers insisting on using the e-mail and date as the > *head* of the id, instead of some fast-varying value like a sha-1 > digest. Well, they thought that a bare series of hex digits are too intimidating and put something familiar in front of the hash. Unfortunate, yes.