Fossil cannot remove existing history. So removing only one dir and the associated history is not possible.
Why don't you just update the files to be sorted and after that always keep adding them sorted? The diffs up until now will still be noisy, but from now on they will be more readable and you will keep the previous history. On Mon, Dec 4, 2017 at 6:29 AM, Andy Bradford <amb-fos...@bradfords.org> wrote: > Thus said Paolo Bolzoni on Fri, 01 Dec 2017 09:18:10 +0100: > >> What happened is that I got an update of these files and the new >> version changed the order of most the keys, but it changed only few >> values. However, this changes in the order made the fossil diffs >> confusing and large. > > What do you mean by, ``I got an update of these files?'' > > Does that mean that someone else committed some changes to your > repository and when you did ``fossil update'' you got all their changes? > And you want to change them? > > Or does that mean you made some changes to the working checkout, and > committed them? > > Or does it mean that you made some changes to your working checkout and > decided you don't like the changes? > >> If I could go back, I would store all the files sorted, and here comes >> the question. Can I make fossil forget all the changes in dir1? so I >> put back them back properly sorted? > > Yes. You can make fossil ``forget'' those changes, but how that is > accomplished depends largely on your answer to my question above. > > Andy > -- > TAI64 timestamp: 400000005a24dd6f > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
