On 15 Nov 2022, Evgeny Kotkov wrote:
Evgeny Kotkov <evgeny.kot...@visualsvn.com> writes:
Perhaps we could transition into that state by committing the
patch
and maybe re-evaluate things from there. I could do that,
assuming
no objections, of course.
Committed the patch in https://svn.apache.org/r1905324
I'll try to handle the related tasks in the near future.
Thank you, Evgeny! Just to make sure I understand correctly --
the status now on the 'pristines-on-demand-on-mwf' branch is:
1) One can do 'svn checkout --store-pristines=no' to get an
entirely pristine-less working copy. In that working copy,
individual files will be hydrated/dehydrated automagically on an
as-needed basis.
2) There is no command to hydrate or dehydrate a particular file.
Hydration and dehydration only happen as a side effect of other
regular Subversion operations.
3) There is no way to rehydrate the entire working copy. E.g.,
something like 'svn update --store-pristines=yes' or 'svn hydrate
--depth=infinity' does not exist yet.
4) Likewise, there is no way to dehydrate an existing working copy
that currently has its pristines (even if that working copy is at
a high-enough version format to support pristinelessness). E.g.,
something like 'svn update --store-pristines=no' or 'svn dehydrate
--depth=infinity' does not exist yet.
Is that all correct?
By the way, I do not think (2), (3), and (4) are blockers. Just
(1) by itself is a huge step forward and solves issue #525; IMHO,
once the tests are ready, we could merge it and release it to the
world.
Best regards,
-Karl
