On Wed, Dec 24, 2008 at 12:00:37PM +1100, "Trent W. Buck" <[email protected]> wrote: > Miklos Vajna <[email protected]> writes: > > > Let's say you create a repo: [...] > > > > (2) is about: rename A to B, remove B - so B was not in the repo and > > after the patch A won't be either. > > > > (4) is about: remove B, rename A to B - so A and B were in the repo > > and after the patch only B will be, with the contents of A. > > > > So you can see the order of remove and move matters a lot. > > Assuming I've understood the implications correctly, I don't think this > is a bug. However I don't think I *have* understood; I need a > blackboard to nut this one out.
Sure, the fact that the order of applying hunks matters is not a problem - I think. > > Now if you do a darcs changes --xml -s, then you *always* get the moves > > first, so you can't decide what situation are you in. > > > > Is this a feature? Or should I report it as a bug? > > The output of changes here is arguably a bug, due to the case you > describe above. By all means report it to the BTS -- even if consensus > is that it *isn't* a bug, it means we then have a record of the non-bug > and a flag of "WONTFIX" against it -- which will help future bug > reporters. OK, http://bugs.darcs.net/issue1281.
pgpbkbRL8TpBV.pgp
Description: PGP signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
