Check out this commit http://www.fossil-scm.org/index.html/info/a1814d5015. Looks an attempt to address this issue.
On Wed, Feb 16, 2011 at 10:19 AM, Louis Hoefler <louis.hoef...@gmx.de>wrote: > Following szenario: > > I have two computers. > > On computer 1, I create a fossil with some work. > > Now I commit my work and copy the fossil to computer 2. > I rename files on computer 2, do some other work, and commit. > > I make some filechanges on computer 1, and commit. > Now I have two fossils who are out of sync. > > I come back home and overwrite the fossil from computer > 1 with the one from computer 2 (where I renamed files). > > Now, after I do a fossil update, the (modified) files > on computer 1 are deleted and fossil stops the update > process, becouse it can not find the newly renamed files. > > I do not really understand the logic behind this error but, > if this isnt the case: Files should be deleted only, > if they have not changed (in case of a rename they should > not be deleted if the last known version in fossil differs > from the current file on disk). > > Greetings, Louis > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- Justin Mazzi
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
