Dear list, I have a fairly large set of files, (a bit fewer than 60,000) containing a simple key-value store in text format.
Being it so huge, and since I need to do edit only few files (besides the customer needs only the changed ones) i organized my project in this way: dir1/ original files dir2/ the files I changed and kept it under fossil revision control. However, the original files are not sorted in any way; so I usually do the commits in two stages: (one) coping and sorting the original file from dir1 to dir2 and committing, (two) do my edits on the dir2 copy and commiting. Doing so, the diffs are very clear. 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. I would like to see the changes better and avoid this problem in the future. 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. Ideally I would be able to shun the whole history of dir1, so I can add it sorted and update it. What can I do? Any suggestion? Cheers, Paolo _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
