From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel,gmane.emacs.gnus.general Subject: Re: The Gnus repository is switching to Git as of 2010-04-19 Date: Tue, 20 Apr 2010 23:11:13 -0400 Message-ID: References: <878w8jmjly.fsf@lifelogs.com> <87fx2qgrdw.fsf@lifelogs.com> <878w8hevp6.fsf@lifelogs.com> <87aasxmyo8.fsf@uwakimon.sk.tsukuba.ac.jp> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1271819550 1445 80.91.229.12 (21 Apr 2010 03:12:30 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 21 Apr 2010 03:12:30 +0000 (UTC) Cc: Ted Zlatanov , ding@gnus.org, emacs-devel@gnu.org To: "Stephen J. Turnbull" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Apr 21 05:12:29 2010 connect(): No such file or directory 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.69) (envelope-from ) id 1O4QMV-0006oI-SN for ged-emacs-devel@m.gmane.org; Wed, 21 Apr 2010 05:12:28 +0200 Original-Received: from localhost ([127.0.0.1]:56655 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O4QMU-0006IN-Ry for ged-emacs-devel@m.gmane.org; Tue, 20 Apr 2010 23:12:26 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O4QLP-00057Y-UP for emacs-devel@gnu.org; Tue, 20 Apr 2010 23:11:20 -0400 Original-Received: from [140.186.70.92] (port=37818 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O4QLO-00055Z-CR for emacs-devel@gnu.org; Tue, 20 Apr 2010 23:11:19 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O4QLM-0003J5-05 for emacs-devel@gnu.org; Tue, 20 Apr 2010 23:11:18 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:10540 helo=ironport2-out.pppoe.ca) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O4QLL-0003Iz-Tn for emacs-devel@gnu.org; Tue, 20 Apr 2010 23:11:15 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEABoKzktMCqI2/2dsb2JhbACcEHK/MoUPBIt1 X-IronPort-AV: E=Sophos;i="4.52,247,1270440000"; d="scan'208";a="61539092" Original-Received: from 76-10-162-54.dsl.teksavvy.com (HELO ceviche.home) ([76.10.162.54]) by ironport2-out.pppoe.ca with ESMTP; 20 Apr 2010 23:11:13 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id 6E904660DC; Tue, 20 Apr 2010 23:11:13 -0400 (EDT) In-Reply-To: <87aasxmyo8.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Wed, 21 Apr 2010 09:33:59 +0900") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.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:123953 gmane.emacs.gnus.general:69613 Archived-At: >> I know that's how it works. But I don't know what [git's >> automatic-detection-implementation of copy/rename] means in terms of >> the behavior when merging changes, including addition/removal of files. >> IIUC it understands movement of files, but does it understand movement >> of directories (e.g. if Gnus adds a new file lisp/gnus-new.el, will it >> appear in Emacs as lisp/gnus/gnus-new.el or lisp/gnu-new.el?; similarly >> if Emacs adds a new file lisp/new.el will it appear in Gnus as >> lisp/new.el?). > Bazaar can't handle that and won't anytime soon as a standard feature I think your "that" is not what I was talking about, because I know for a fact it works. What I'm talking about is to just move directories around in a branch: no need for nested trees or any such thing, no restriction to "same layout" either. >> It should be just as easy for a branch as for the trunk. > Maybe. I worry about ghost revisions appearing when you do a git->bzr > sync, and that's where they are most likely since git users branch > with abandon then abandon the branches, while it's no fun to try to > work with Bazaar that way. Note that ghost revisions causes nasty > bugs in bzr as recently as a few weeks ago. Ghost revisions are a problem for Bzr implementers, not users. Stefan