On Tue, 29 Mar 2005 20:16:55 +0200, Jan Hudec <[EMAIL PROTECTED]> wrote: > On Tue, Mar 29, 2005 at 11:59:06 -0600, Gustavo C�rdova Avila wrote: > > Florian Weimer wrote: > > > > >* Magnus Therning: > > > > > > > > >>Of course Arch doesn't suffer from the shortcoming, and it passes the > > >>"litmus test" with flying colours. > > >> > > >> > > >Really? Does it correctly handle newly added files in renamed > > >directories? > > > > > > > > > > > Such a trivial test? > > > > It would really surprise me if you can find such a use-case which fails. > > I have not tried, but I think this would not work out: > > 1) Have a project with 'foo' directory. > 2) Branch it > 3) On one branch rename the 'foo' directory to 'bar' > 4) On another branch create file 'foo/baz' > 5) Merge. > > Now correct behaviour would be to place the 'baz' file in the renamed > directory.
I think your definition of "correct behavior" is potentially debatable, but I agree that this is probably the best definition and I did confirm that it does not work like that. The changeset records the addition of the file using named path elements, not the logical identities of the path elements. Tom, can you comment on this? This seems like a pretty fundamental design point. Bob _______________________________________________ Gnu-arch-users mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/
