To: gnu-arch-users@gnu.org
References: <20041013014319.GA26002@unununium.org>
From: Miles Bader <miles@lsi.nec.co.jp>
System-Type: i686-pc-linux-gnu
Blat: Foop
Date: Wed, 13 Oct 2004 10:50:30 +0900
In-Reply-To: <20041013014319.GA26002@unununium.org> (Phil Frost's message of
	"Tue, 12 Oct 2004 21:43:19 -0400")
Message-ID: <buo655ffkt5.fsf@mctpc71.ucom.lsi.nec.co.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Gnu-arch-users] Re: [BUG] merging new files into a renamed
 directory looses the file
Precedence: list
Reply-To: Miles Bader <miles@gnu.org>
Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Status: RO
Content-Length: 998
Lines: 23
Phil Frost <indigo@bitglue.com> writes:
> Expected behavior:
>
> after merging 'main' into 'B', the file that was added in 'A' is created
> in the now renamed directory 'bar', formerly 'fu'.
>
> Observed behavior:
>
> after merging 'main' into 'B', a directory 'fu' is created, with the new
> file in it. tree-lint reports this directory as "would be source if it
> had an id."

I believe this is a known bogosity in the way file addition/deletion is
represented in changesets -- they use absolute names, not
filename + id-tag of their directory.  I find it very annoying too
(bites me a coupble of times a month).

Unfortunately I think this requires an archive-format rev to fix, so
it's not something that will change soon.

-Miles
-- 
"1971 pickup truck; will trade for guns"


_______________________________________________
Gnu-arch-users mailing list
Gnu-arch-users@gnu.org
http://lists.gnu.org/mailman/listinfo/gnu-arch-users

GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/