[
https://issues.apache.org/jira/browse/SVN-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17502953#comment-17502953
]
Daniel Shahaf commented on SVN-4889:
------------------------------------
If we don't have a per-wc knob, {{svn upgrade --compatible-version=1.15}}
becomes a command that deletes pristines. This can be a problem if the
repository is inaccessible or no longer exists (cf. [upgrade_tests #16
replaced_files()|https://issues.apache.org/jira/browse/SVN-4891?focusedCommentId=17502948#comment-17502948]).
So, having this knob would make {{svn upgrade}} safer.
> Pristines-on-demand: per-WC config
> ----------------------------------
>
> Key: SVN-4889
> URL: https://issues.apache.org/jira/browse/SVN-4889
> Project: Subversion
> Issue Type: Improvement
> Reporter: Julian Foad
> Priority: Major
>
> [dev@
> thread|https://lists.apache.org/thread/qw2cngzc22kvzw8ro77jfqpoz9nhm3fx]
> "[PATCH] Sketch of per-user/per-wc config for pristines-mode"
> The #SVN-525 feature (aka WCs without pristines, pristines-on-demand,
> bare-WCs) needs a per-WC configuration capability.
> The thread linked above sketches one way of going about such a configuration.
> Other ways are possible too.
> This is not strictly needed for the first release or "minimum viable product"
> (MVP) of the #525 feature, as the feature can be activated by upgrading the
> selected WCs to 1.15 format and will default to remaining disabled for other
> WCs.
> It MIGHT be good to add the low level flagging mechanism now, because that
> might help any future new WC capability to co-exist in a 1.15 format WC.
> Otherwise any such new capability would have to assume that
> pristines-on-demand is always enabled in a 1.15 format WC, and so have to
> bump to another new format to make it optional. It is not clear which would
> be more effort.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
