[
https://issues.apache.org/jira/browse/SVN-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511156#comment-17511156
]
Julian Foad commented on SVN-4890:
----------------------------------
As Daniel writes in the linked thread, "Isn't this orthogonal to the
multi-wc-format work? To date it has always been possible to upgrade an
external without upgrading its parent [...] The fact that the client doing the
upgrade has multi-wc-format support doesn't affect this logic."
So I am changing this issue to not be a blocker for SVN-4883 (multi-wc-format).
> multi-wc-format: should we forbid upgrading an external WC to mismatch its
> parent WC format?
> --------------------------------------------------------------------------------------------
>
> Key: SVN-4890
> URL: https://issues.apache.org/jira/browse/SVN-4890
> Project: Subversion
> Issue Type: Improvement
> Reporter: Julian Foad
> Priority: Major
> Labels: api
>
> Daniel Shahaf wrote, in dev@ email "multi-wc-format: upgrading externals"
> (https://mail-archives.apache.org/mod_mbox/subversion-dev/202202.mbox/%3C20220219144836.GA2817%40tarpaulin.shahaf.local2%3E):
> multi-wc-format/BRANCH-README mentioned this:
> > [*] New externals working copies must inherit the format from their
> > parent working copy, because mixed-format working copies are a) a
> > Bad Thing, and b) defeat the purpose of this feature, which is
> > support for multiple versions of the client in the same working
> > copy.
> Upgrading a parent working copy upgrades external wc's too. However,
> upgrading an external succeeds. Judging by the quoted remark, should
> «svn upgrade --compatible-version=$N /path/to/external» error out unless
> the external's parent working copy is already at version $V?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
