Mikhael Goikhman wrote:
> I think ~/.arch-params/auto-cacherev-frequency would be good.
>
> Having a tree stored file ({arch}/=auto-cacherev-frequency)
> may be useful
> too, but it can't be used for initial 'get' obviously.
I think a per-tree value make more sense. Small trees new smaller
number; big tree may prefer bigger number. Also, It is more cleaner in
the situation of multiple committers if everyone cacherev in the same
frequency. Only the fetching invoked from within diff/star-merge... will
be able to use the per-tree number though; get will have to use the
default.
>
> I have a question. If there is an automatic cacherev every 50
> revisions,
> I suppose this happens on base-0, patch-50, patch-100 and so on, so
> that if patch-123 is requested, there is a good estimation
> that patch-100
> is cacherev'd. Is this correct, or it may also auto-cacherev
> patch-111?
Right now it just does 0, 50, 100, ... If patch-123 is requested, then
there are two possible ways to fetch it:
1, if you happen to have a patch level between 51 and 122 in revlib or
pristine, get that and patch on.
1, otherwise, get the cacherev patch-100 and patch on
>
> Another thing. If I understand correctly, you only assign cost to
> applying a patch. But not to fetching different things from archive.
> (Ideally, different costs for local and remote archives.)
Right now I try not to cross the archive boundary. So the tradeoff is
really between fetching patches or fetching cacherev from the same
archive.
>
> Regards,
> Mikhael.
>
Derek
_______________________________________________
Gnu-arch-users mailing list
Gnu-arch-users@gnu.org
http://lists.gnu.org/mailman/listinfo/gnu-arch-users
GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/
