>> * the number 50 is hard coded; it really should be a value that the user
>> can customize.
> Before this is viable, it *must* be possible to turn this behaviour
> off. On large trees, cacherevs are massively wasteful of space;
> revision libraries are often a more efficient solution.
I use a remote archive with a local revlib.
Cacherevs are rarely useful for my use, but I think every version should
have basically 1 cacherev, basically caching the latest revision.
This way people doing a "get" of the head of a version don't have to apply
hundreds of patches. Cacherevs on older revisions aren't very important in
my experience.
Note that when I do a "update", I'd rather apply 20 patches than downlooad
a cacherev, but I think the backward patching algorithm had a heuristic
for that.
Stefan
_______________________________________________
Gnu-arch-users mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnu-arch-users
GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/
