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 not a
fetch-at-point-of-access design.
This seems like a good principle for the long run (and
well-articulated above, thank you!).
Is the above happening in MVP? 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-WC setting that means
"store no pristines in this WC" and that's that.
That means it would be up to the user to use the available
workarounds if they need to do things (like local diff) that would
require a pristine. Fortunately those workarounds are easy: they
just involve copying a file sometimes before you start working on
it :-).
Just to be be super clear: my question here is solely about MVP --
about the first released version of a usable 525-enabled
Subversion -- not about the longer term plans, which I agree are
excellent and will make the feature even better.
Best regards,
-Karl
