[
https://issues.apache.org/jira/browse/SVN-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17517473#comment-17517473
]
Julian Foad edited comment on SVN-4886 at 4/5/22 2:32 PM:
----------------------------------------------------------
The idea came to me from what [Johan wrote on
2022-01-21|https://lists.apache.org/thread/1qttmnqt3xvb9rny6nnmso771xs18rjm]
re. use case upgrading existing WCs on a build farm:
"[step 1:] Set a system-wide flag to make pristines-on-demand the default for
new WC's. [step 2:] upgrade/convert the existing WCs..."
That is not a direct request to configure the WC version, but either the
pristines-on-demand config will have to imply also a WC version high enough to
support it, or a separate WC version option will be needed as well.
was (Author: julianfoad):
The idea came to me from what [Johan wrote on
2022-01-21|https://lists.apache.org/thread/1qttmnqt3xvb9rny6nnmso771xs18rjm]
re. use case upgrading existing WCs on a build farm:
"[step 1:] Set a system-wide flag to make pristines-on-demand the default for
new WC's. [step 2:] upgrade/convert the existing WCs..." That is not directly a
request to configure the WC version
> multi-wc-format: config for default WC version for checkout & upgrade
> ---------------------------------------------------------------------
>
> Key: SVN-4886
> URL: https://issues.apache.org/jira/browse/SVN-4886
> Project: Subversion
> Issue Type: Improvement
> Reporter: Julian Foad
> Priority: Major
>
> Let the default "compatible version" be specified in the user config. (That
> is, the default version for 'checkout' and 'upgrade', which are the places
> where a version can be specified.)
> This configured version should be overridden by any '--compatible-version'
> command-line option.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
