On Tue, Sep 2, 2014 at 5:07 PM, <sky5w...@gmail.com> wrote: > While disabling checksums helps with speed > http://www.fossil-scm.org/index.html/help?cmd=settings > It does not help with redundant binary images in the repo. > For that, you have to shun and rebuild. > If you could flag a file as "Keep latest only", that would be less > painless. I don't mind the artifact overhead of a changed binary file, but > it hurts to have the data stored too. > > (1) Fossil *does* store binary files as diffs from their predecessor, if they are sufficiently similar (that is, if the diff is smaller than the file itself). the problem is that with compressed images, changing a single pixel can potentially change most bytes of the file, making a diff pointless.
(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. -- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
