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
TL;DR: OK to merge multi-wc-format to trunk soon?
Having worked with it these last few weeks, I think the essential pieces
are in place for multi-wc-format to be merged to trunk.
I am still working on the last pieces of pristines-on-demand rebased on
top of this branch: fixing tests to work
r1897943 makes the default for "--compatible-version" (and tests) be "1.8".
- Julian
On Thu, Feb 10, 2022 at 7:25 AM Julian Foad wrote:
>
> It strikes me now, given Subversion's "mature, stable" phase of life,
> that we should default to backward compatibility.
>
> Change the default to --compatible-version=1.8 (same as =1.14), instead
> of 1.15 (format 32). Both for "checkout"
It strikes me now, given Subversion's "mature, stable" phase of life,
that we should default to backward compatibility.
Change the default to --compatible-version=1.8 (same as =1.14), instead
of 1.15 (format 32). Both for "checkout" and "upgrade". The user will
need to specify
> I think this branch is now ready to merge to trunk.
I am now asking for review.
To help, here is an overview of the branch changes, compiled from its
log messages:
Instead of supporting just one format, introduce a
I think this branch is now ready to merge to trunk.
In a series of commits I have added '--wc-format-version' argument to
the C and Python test suite framework on this branch, and tested that it
works with both '1.15' (the default, WC format 32) and '1.14' (wc format 31).
I tested that the
On 03.02.2022 17:30, Julian Foad wrote:
Julian Foad wrote:
Branko Čibej wrote:
way to report the actual format (from the wc-db) through libsvn-wc to
the client?
Ah yes, there is no API for that, [...]
These exist on the branch currently ("*_supported_*" are new on the branch):
- At
Julian Foad wrote:
> Branko Čibej wrote:
>> way to report the actual format (from the wc-db) through libsvn-wc to
>> the client?
>
> Ah yes, there is no API for that, [...]
These exist on the branch currently ("*_supported_*" are new on the branch):
- At libsvn_client (public):
Branko Čibej wrote:
> I still seem to remember we have a bit missing on the multi-wc-format
> branch, but I can't remember what ... maybe we don't currently have a
> way to report the actual format (from the wc-db) through libsvn-wc to
> the client? Or has that been fixed?
Ah yes, there is
On 02.02.2022 20:49, Julian Foad wrote:
[...] a single test [...] It doesn't seem necessary to automate
running over the whole test suite with (format < SVN_WC__VERSION) [...]
Meh. That's only true for the place-holder code as present on the
'multi-wc-format' branch, where the code reports
> [...] a single test [...] It doesn't seem necessary to automate
> running over the whole test suite with (format < SVN_WC__VERSION) [...]
Meh. That's only true for the place-holder code as present on the
'multi-wc-format' branch, where the code reports multiple formats are
supported but there
We need multi-wc-format for issue #525 pristines-on-demand, as discussed
in the long thread "A two-part vision for Subversion and large binary objects."
It is designed to be a generic framework, not tied to a specific
feature, so while I will do some tests on a local merge of
pristines-on-demand
13 matches
Mail list logo
