Thus said Paolo Bolzoni on Thu, 30 Nov 2017 12:40:17 +0100: > It worked fairly well until I received an unexpected update of the > original files. I unpacked the new files in dir1 and fossil detected > hundreds of changes; looking better however this changes are mostly > just order changes.
Can you give a more concrete example? I'm not sure what you mean by they are ``mostly just order changes.'' What order changed? > So, my problem is... what is the best way to proceed? I can start a > new fossil repository, but I would lose the history in dir2. I can > delete dir1 and recommit the two versions sorted, but it would add > lots of needless changes in the repo again. What exactly are you doing here? How can you lose history of dir2 if the history is committed to Fossil? Again, I think additional details would be helpful. Some fossil and shell commands that show how to reproduce your situation would be useful. Thanks, Andy -- TAI64 timestamp: 400000005a2072ee _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
