Mark Phippard wrote:
>> Update starts by hydrating. That means it WILL download any missing
>> pristines of modified files, regardless whether any newer revision
>> will be found.
>
> Does the possibility exist to optimize this at all? [...]
To understand, we need to recap that this design is bas
Merged to trunk now. Testers, enhancers welcome. More below.
Please try it out if you haven't.
The basics:
wc format 31:
- compatible with svn 1.8 to 1.14 and now 1.15-dev
wc format 32:
- compatible with svn 1.15-dev only,
- as yet introduces no schema changes (we expect those to come when
I committed the proposed fix in r1898184:
[[[
On the 'pristines-on-demand-on-mwf' branch: fix authz_tests.py 31.
This test runs an 'update' after read access permission has been removed
from a repository path. The text base sync code errored out when it
tried to download this text base.
We fix it
On 18 Feb 2022, Julian Foad wrote:
To understand, we need to recap that this design is based around
a
simple invariant: whenever a file is seen to be locally modified,
at the
next convenient opportunity we will download its base; and when
seen to
be not-modified we will discard its base. It is
Karl Fogel wrote:
> Is the above happening in MVP?
Yes. I was describing what Evgeny created last year in the
'pristines-on-demand' branch.
> I ask because my understanding of
> MVP was that it's not doing this opportunistic fetching/discarding
> of bases, but rather that it's a simple per-W
On Fri, Feb 18, 2022 at 3:21 PM Julian Foad wrote:
>
> Karl Fogel wrote:
> > Is the above happening in MVP?
>
> Yes. I was describing what Evgeny created last year in the
> 'pristines-on-demand' branch.
>
> > I ask because my understanding of
> > MVP was that it's not doing this opportunistic fet
6 matches
Mail list logo