From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Karl Fogel Newsgroups: gmane.emacs.devel Subject: Re: Repo cpnversion progress report Date: Fri, 31 Jan 2014 11:31:10 -0600 Message-ID: <87iot0f481.fsf@ktab.red-bean.com> References: <20140130195557.GA8405@thyrsus.com> <83iot16u66.fsf@gnu.org> <20140130214201.GA9204@thyrsus.com> <83ha8k7fp0.fsf@gnu.org> Reply-To: Karl Fogel NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1391189481 7194 80.91.229.3 (31 Jan 2014 17:31:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 31 Jan 2014 17:31:21 +0000 (UTC) Cc: esr@thyrsus.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 31 18:31:27 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 1W9Hw5-0005MQ-Ev for ged-emacs-devel@m.gmane.org; Fri, 31 Jan 2014 18:31:25 +0100 Original-Received: from localhost ([::1]:57247 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W9Hw5-0005jp-25 for ged-emacs-devel@m.gmane.org; Fri, 31 Jan 2014 12:31:25 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59693) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W9Hvy-0005hR-4B for emacs-devel@gnu.org; Fri, 31 Jan 2014 12:31:22 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W9Hvt-0002LL-IE for emacs-devel@gnu.org; Fri, 31 Jan 2014 12:31:18 -0500 Original-Received: from mail-ie0-x22e.google.com ([2607:f8b0:4001:c03::22e]:48098) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W9Hvt-0002LE-CR; Fri, 31 Jan 2014 12:31:13 -0500 Original-Received: by mail-ie0-f174.google.com with SMTP id tp5so4613801ieb.19 for ; Fri, 31 Jan 2014 09:31:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:to:cc:subject:references:reply-to:date:in-reply-to :message-id:user-agent:mime-version:content-type; bh=9ctGfPBNSuvNiLimkMWwKubHc7cmln38mbpgv9dHluU=; b=dLxQLRXrb8BF2fLJk+P0VWU+9doPXqRnGKkKmMMxuQ7qrdWHlSmrrfKDvxcOwbcSOy L5Sux173LLsfDdML1FMH/mO0RBn00y34qwxTaMLG6G9agOo1VQfp6JDNil2AqCkP7B2y W16mdgKytzzr6HMOcB330gVYYc+Z19Cw/8ERDY70SdPVZP8aUZ1eN5YAShrbhGLodBrZ 9OK/OJBP3GpyWmY7cE7Atb9xD3LTa8ll7qL1sr9O0rU/zoYCNckia+BU0qC15oEIgnph iyyDsq3m5nJs6VV6s1Uv5WV4XM5VuCaIDMFqoKjLjEfLeZTmLZYZjX7DXPZVjzBebeBA hmzA== X-Received: by 10.50.138.98 with SMTP id qp2mr41302526igb.27.1391189472374; Fri, 31 Jan 2014 09:31:12 -0800 (PST) Original-Received: from ktab.red-bean.com (74-92-190-113-Illinois.hfc.comcastbusiness.net. [74.92.190.113]) by mx.google.com with ESMTPSA id ft2sm33244753igb.5.2014.01.31.09.31.11 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Fri, 31 Jan 2014 09:31:11 -0800 (PST) In-Reply-To: <83ha8k7fp0.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 31 Jan 2014 09:50:35 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:4001:c03::22e 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:169282 Archived-At: Eli Zaretskii writes: >They are not meaningless, since, as you correctly recommend, the bzr >repo should be kept frozen at the point of the switch, rather than >deleted. If something goes wrong during the conversion, and someone >needs to do some archeology later, these numbers might help. > >So I suggest to make the replacements like this: > > "rev 102609" => "2010-12-08T08:09:27Z!kfogel@red-bean.com (bzr r102609)" > ^^^^^^^^^^^^^ I agree with Eli's point above, FWIW (and not just because he happened to use one of my (sadly rarer than I would like) commits as an example). Preserving the bzr revision number isn't very distracting -- anyone spelunking through this stuff already has good vgrep goggles on -- and provides a valuable trail in the event of an urgent forensic expedition. As we all know, such expeditions occur more often than we expect, even after we adjust our expectations accordingly :-). I don't agree with Eli's comments in a later mail about how he wasn't sure we should entrust this job to ESR. It's a complex, time-consuming, and apparently thankless task; IMHO ESR is doing a good job considering all the inputs involved (both human and machine). -K