(2) Fossil's purpose is to be able to recreate historical versions of the project - exactly. It cannot do that if historical images have been deleted. I understand the purity intended, but continue to be frustrated by it. :) I merely seek an automated way within Fossil to manage garbage. Re-repoing to delete spam or 'add *.*' mistakes is quite painful.
On Tue, Sep 2, 2014 at 5:19 PM, Warren Young <war...@etr-usa.com> wrote: > On 9/2/2014 15:07, sky5w...@gmail.com wrote: > >> If you could flag a file as "Keep latest only", that would be less >> painless. >> > > That wouldn't work for me. I want the past versions of the image. [*] > > The branch I made of the web app three years ago won't run right with the > current bitmaps. The new ones may be different sizes, have a different > design esthetic, etc. > > With repo-cksum on, Fossil has an O(N) complexity component. Without it, > you only have the logarithmic time complexities due to the tree structures > of the DB. > > > [*] Well, I suppose I could go through and weed out a few bad ideas, but > that goes against Fossil's nature. > > _______________________________________________ > 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
