[
https://issues.apache.org/jira/browse/SVN-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Foad updated SVN-4887:
-----------------------------
Fix Version/s: 1.15-proposed
(was: 1.15.0)
> multi-wc-format: clarify/unify option names for compatible-version
> ------------------------------------------------------------------
>
> Key: SVN-4887
> URL: https://issues.apache.org/jira/browse/SVN-4887
> Project: Subversion
> Issue Type: Improvement
> Reporter: Julian Foad
> Priority: Major
> Labels: api
> Fix For: 1.15-proposed
>
>
> Clarify/unify the option names used for specifying the WC format compatible
> version.
> Subversion commands also have other compatibility concerns besides the WC
> format. (repo format, for one.)
> Current option names:
> * --compatible-version # for 'svnadmin': repository version
> * --compatible-version # for 'svn': WC version
> * --wc-format-version # for the tests: WC version
> Suggestions for WC version everywhere ('svn' and tests):
> * --wc-compatible-version
> * --wc-compatible-format
> Consider also the 'svn info --show-item' label(s):
> * --show-item=wc-format
> * --show-item=wc-compatible-version
> Consider also the list of WC formats shown in 'svn --version', currently:
> {code:java}
> Supported working copy (WC) formats:
> * compatible with Subversion v1.8 to v1.15 (WC format 31)
> * compatible with Subversion v1.15 (WC format 32){code}
> This could usefully show the exact command option syntax to use, e.g.
> {code:java}
> * --wc-compatible-version=1.8 (up to v1.15) (WC format 31)
> * --wc-compatible-version=1.15 (WC format 32){code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
