From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen J. Turnbull" Newsgroups: gmane.emacs.devel Subject: Re: Switching to bzr: what remains to be done? Date: Tue, 09 Dec 2008 09:59:03 +0900 Message-ID: <877i6a9nag.fsf@xemacs.org> 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 1228784024 13120 80.91.229.12 (9 Dec 2008 00:53:44 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 9 Dec 2008 00:53:44 +0000 (UTC) Cc: Karl Fogel , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 09 01:54:47 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 1L9qsB-0001xJ-9V for ged-emacs-devel@m.gmane.org; Tue, 09 Dec 2008 01:54:47 +0100 Original-Received: from localhost ([127.0.0.1]:58602 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L9qr0-00042w-D5 for ged-emacs-devel@m.gmane.org; Mon, 08 Dec 2008 19:53:34 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L9qqw-00042e-8e for emacs-devel@gnu.org; Mon, 08 Dec 2008 19:53:30 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L9qqt-00042S-RE for emacs-devel@gnu.org; Mon, 08 Dec 2008 19:53:28 -0500 Original-Received: from [199.232.76.173] (port=33939 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L9qqt-00042P-MQ for emacs-devel@gnu.org; Mon, 08 Dec 2008 19:53:27 -0500 Original-Received: from mtps01.sk.tsukuba.ac.jp ([130.158.97.223]:40798) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1L9qqt-0002jQ-5e for emacs-devel@gnu.org; Mon, 08 Dec 2008 19:53:27 -0500 Original-Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by mtps01.sk.tsukuba.ac.jp (Postfix) with ESMTP id 84D4A1535AC; Tue, 9 Dec 2008 09:53:17 +0900 (JST) Original-Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id A45181A31BB; Tue, 9 Dec 2008 09:59:03 +0900 (JST) In-Reply-To: X-Mailer: VM 8.0.12-devo-585 under 21.5 (beta28) "fuki" 83e35df20028+ XEmacs Lucid (x86_64-unknown-linux) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) 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:106699 Archived-At: Stefan Monnier writes: > 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. Sorry I can't help with the actual work, but I have some related experience to describe. cvs2svn did a great job for me converting the XEmacs repo to git's fastimport format. The XEmacs repo is an unholy mess, too, I was quite surprised at how well cvs2svn handled this. It has some kind of update facility (AIUI fastimport is just a format for describing commits). I'm not sure if bzr has bulletproof fastimporter yet, but I know this has come up on the list lately. Anyway, I recommend a look at cvs2svn, and maybe encouraging bzr work on fastimport. tailor is another option, but I've found tailor to require a lot of care and feeding, at least at first. The receiving backend was Mercurial which was implemented as a plugin from the libraries, not by invoking hg itself. However the command line interface is more stable, which seems to be the source of my difficulties. > We have lived without any renaming or merge info in our CVS, Going through git or another VCS that does automatic rename detection might be an option. > 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. I think pretty much all popular tools can do this.