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 13:31:37 -0600 Message-ID: <8761p0eyna.fsf@ktab.red-bean.com> References: <20140130195557.GA8405@thyrsus.com> <83iot16u66.fsf@gnu.org> <20140130214201.GA9204@thyrsus.com> <83ha8k7fp0.fsf@gnu.org> <87iot0f481.fsf@ktab.red-bean.com> Reply-To: Karl Fogel NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1391196708 29871 80.91.229.3 (31 Jan 2014 19:31:48 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 31 Jan 2014 19:31:48 +0000 (UTC) Cc: Eric Raymond , Eli Zaretskii , Emacs developers To: Juanma Barranquero Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 31 20:31:54 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 1W9Jof-0004zH-S8 for ged-emacs-devel@m.gmane.org; Fri, 31 Jan 2014 20:31:54 +0100 Original-Received: from localhost ([::1]:57691 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W9Jof-0005R9-86 for ged-emacs-devel@m.gmane.org; Fri, 31 Jan 2014 14:31:53 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57438) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W9JoX-0005Ps-Jr for emacs-devel@gnu.org; Fri, 31 Jan 2014 14:31:51 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W9JoR-0005Hh-Dm for emacs-devel@gnu.org; Fri, 31 Jan 2014 14:31:45 -0500 Original-Received: from mail-ig0-x22e.google.com ([2607:f8b0:4001:c05::22e]:59777) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W9JoR-0005Ga-89; Fri, 31 Jan 2014 14:31:39 -0500 Original-Received: by mail-ig0-f174.google.com with SMTP id hl1so46426igb.1 for ; Fri, 31 Jan 2014 11:31:38 -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=/16ku0/2qmJFGl/VzdXEWFtBKSoAoxGeVe8yJJi2NHA=; b=niMeQYmDzX6UuBgY5ZBg405dQ0QIv0cKXdjPOaigb4opu4WzQA6+kGXD7+KXIPH3ol s1hO+J6d7Pmgu4xamH1GydZ599zEISPEambVmJfU52AVdUG/TWUg2x6is6igE375GxAR oRygFhYMR5kwOce+Kv2PXbvJ5vu4MU5vqkgt1mFBfCjbsmFhEsEEBb7lfU5GkGmsRcia FfzH8M/vON1NANpJDT0ECkf+sJL4TpjszIcrRsPt7N1IawBdN9ZttOx+lFiDicQBaPV0 /iYXgI8aR1PnLzPsUVH6PHzfTqmfFKK1JEAeyuTVVL1vZsnGQJOyC8gXA3rm2+Ee3cne uYfg== X-Received: by 10.50.43.131 with SMTP id w3mr87381igl.17.1391196698513; Fri, 31 Jan 2014 11:31:38 -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 kt2sm8253119igb.1.2014.01.31.11.31.37 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Fri, 31 Jan 2014 11:31:37 -0800 (PST) In-Reply-To: (Juanma Barranquero's message of "Fri, 31 Jan 2014 18:56:49 +0100") 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:c05::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:169290 Archived-At: Juanma Barranquero writes: >On Fri, Jan 31, 2014 at 6:31 PM, Karl Fogel wrote: > >> 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). > >Well, do you at least agree with him when he says > >> I'm ignored already. You never accepted any argument of mine through >> that long and tiresome "discussion". You are always right and all >> those who disagree with you are always wrong. > >and > >> I never had any influence over that, because you refuse to listen >> to any dissenting arguments, and prefer to stubbornly do what you >> decided was right ahead of any discussion. > >? My impression -- I've followed the discussions, but have not read every single message or subthread -- is that the above is an exaggeration. >Because that's also my feeling about every single switching-to-git >discussion we've had so far. The only thing Eric has backtracked about >is the imminence of switching, and that because Stefan specifically >said that it wouldn't happen during the freeze. The most important fact about all our prior switching-to-git discussions was that always RMS vetoed the idea, explicitly saying that the number of developers who wanted to switch was not relevant to the decision. He even continued saying this after it was obvious that Bazaar was not in any meaningful sense a GNU project. Given that history, I find it ironic that ESR is now being accused of not listening enough :-). In another followup, ESR wrote: >I hear the argument about forensics, but the Bazaar revision numbers >are no more helpful for that than the action stamps. If anything, >spelunking is an argument for appending those numbers to the change >comment of each revision - leaving them in as references would a >bass-ackwards approach to the problem. > >But there's a better way. We're going to have a complete >revision-to-action-stamp map as part of the record. It would be >pretty easy to write Emacs code that uses that map to find revisions >by Bazaar reference number. That's the right solution, IMO. Okay. I'm not able to pay as close attention to the problem as others here are, but if you feel you've got a plan that handles the forensic case well enough, that's fine by me. There are a million ways to convert a bzr history to git. We just need to pick one of those ways that will work for Emacs development. (insert the usual comment about diminishing returns, lather, rinse, repeat?) Best, -Karl