Hello, According to the darcs manual[1]:
"When using darcs replace, the ``new'' token may not already appear in the file--if that is the case, the replace change would not be invertible. This limitation holds only on the already-recorded version of the file." There is an override flag: -f --force proceed with replace even if 'new' token already exists I *think* the main side effect of non-reversibility in darcs is that the patch can not be commuted and therefore depends on previous patches. I do not know enough to say if that is the only side-effect. If you search for 'token' in the manual and read the various sections they cover a fair bit of detail... j. [1] http://abridgegame.org/darcs/manual/bigpage.html At Tue, 02 May 2006 11:37:20 -0700, Thomas Lord wrote: > > > Is anyone familiar enough with DARCS to speak to the > issue of whether token-replace patches are accurately > invertible and, if so, how? Naively: > > s/foo/bar > > is not the inverse transform of: > > s/bar/foo > > -t > > > > _______________________________________________ > 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/ _______________________________________________ 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/
