From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Switching to bzr: what remains to be done? Date: Mon, 08 Dec 2008 14:54:48 -0500 Message-ID: References: <87vdtu332o.fsf@red-bean.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1228766147 20945 80.91.229.12 (8 Dec 2008 19:55:47 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 8 Dec 2008 19:55:47 +0000 (UTC) Cc: emacs-devel@gnu.org To: Karl Fogel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 08 20:56:50 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1L9mDe-00036Q-7d for ged-emacs-devel@m.gmane.org; Mon, 08 Dec 2008 20:56:38 +0100 Original-Received: from localhost ([127.0.0.1]:34026 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L9mCS-0005Sv-Pb for ged-emacs-devel@m.gmane.org; Mon, 08 Dec 2008 14:55:24 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L9mBv-0004qF-JS for emacs-devel@gnu.org; Mon, 08 Dec 2008 14:54:51 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L9mBu-0004oj-OT for emacs-devel@gnu.org; Mon, 08 Dec 2008 14:54:50 -0500 Original-Received: from [199.232.76.173] (port=42994 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L9mBu-0004oT-9X for emacs-devel@gnu.org; Mon, 08 Dec 2008 14:54:50 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:42211) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1L9mBu-00079R-6S for emacs-devel@gnu.org; Mon, 08 Dec 2008 14:54:50 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApsEAGYKPUlLd+Db/2dsb2JhbACBbM0zgwWBJg X-IronPort-AV: E=Sophos;i="4.33,736,1220241600"; d="scan'208";a="30797863" Original-Received: from 75-119-224-219.dsl.teksavvy.com (HELO pastel.home) ([75.119.224.219]) by ironport2-out.teksavvy.com with ESMTP; 08 Dec 2008 14:54:48 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 1B1B68219; Mon, 8 Dec 2008 14:54:48 -0500 (EST) In-Reply-To: <87vdtu332o.fsf@red-bean.com> (Karl Fogel's message of "Mon, 08 Dec 2008 13:59:59 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:106693 Archived-At: > We've been planning to switch to bzr, but haven't really done so yet. > What's still blocking this? > I'll serve as a conduit/organizer in bringing the reasons to bzr > developers, if necessary. (It's related to my work anyway.) I've been using Bzr for my own local branch (on which I do most of my work, after which I get a diff and move it to CVS to commit it). Its performance has been acceptable (not mind-blowing, but not worse than CVS), so I think the main remaining issue to switch is a good repository to start from. Jason Earl has been working on this but hasn't had yet the expected success. Part of the problem is that it seems that depending on the tool we use for the conversion we get some of th desired features, but we can't get them all, it seems: - incremental (the repository at http://bzr.notengoamigos.org/emacs-merges/trunk/ is incremental and is the one I've been using). - includes merge info between various branches (the above repository doesn't include it. There's another that was based on the Git repository, which did have the merge info but could not be updated incrementally). - includes renames. Apparently none of the conversion tools provide that since the info is only available in the Arch repository right now, but that has commits that bundle up several CVS commit into one. - is complete. The http://bzr.notengoamigos.org/emacs-merges/trunk/ seems to have some missing elements (IIRC a few CVS tags were missing). Another issue that AFAIK nobody has worked on, is how are we going to handle the Gnus<->Emacs synchronization in the future. I expect this to be doable somehow, maybe by still going through Arch, but of course it would probably be preferable to do it directly within Bzr, and in any case it will require for someone to figure it out. We have lived without any renaming or merge info in our CVS, so these are not crucial, but since some of that data is available in Arch, it would really be good if we could somehow bring it over to Bzr. Also, being able to update the Bzr repository incrementally from subsequent updates in the CVS is not indispensable, but it would be helpful to make the transition easier. Stefan