Am Samstag, 24. November 2012, 20:28:16 schrieb j. v. d. hoff: > what you propose could easily be filter out from a full recursive search > backward through all revisions (and it would require such a search), right?
Fossil, like many other VCSes, compresses revisions internally, and stores only some sort of deltas. I don't know how it is actually done, but usually, it's some sort of patches. You only have to grep through the patches, they show you when things were added and removed. Expanding all the history should not be necessary to implement this feature. > I would not think this to be the best default behaviour (1000 revisions > to process etc.). I think a "stop at first hit" default is more reasonable > (and maybe more often than not the standard use case) Stopping after a full page or so (like fossil timeline) also could be considered as a reasonable default. -- Bernd Paysan "If you want it done right, you have to do it yourself" http://bernd-paysan.de/
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
