On Tue, Jun 26, 2012 at 11:44 AM, Jacek Cała <[email protected]> wrote:
> I moved a file (say file1.txt) from one dir to another and, in the > same time, changed its name (say, to dir1\file2.txt); it was > relatively long so I forgot about the move. Then I tapped (all names > changed for clarity): > The combinations of add-then-move and move-then-edit (without a commit between the operations) have both historically been problematic for Fossil. i _suspect_ the reason it hasn't ever been "fixed" is because that particular case is "highly philosophical," with no 100% correct behaviour (IMO) and does not cause any data loss (just a bit of confusion the first time it happens and then one doesn't do it again). I may be wrong but think that moves of an added file should be > possible, shouldn't they? > i can't personally say _why_ it's been problematic (design limitation or just an oversight?), but i can assure you that this problem has come up several times in the past few years. i unfortunately cannot suggest a workaround better than what you demonstrated. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
