This is an investigation into changing the "pristines-on-demand"
approach to follow a principle that each operation would only fetch the
pristines it really needs.
I have begun a "user guide" ( notes/i525/i525-user-guide.md ), with the
aim of explaining the principle of operation of the current ap
On 10 Mar 2022, Lorenz wrote:
Daniel Sahlberg wrote:
Den tis 8 mars 2022 kl 14:17 skrev Daniel Shahaf
:
An alternative is to require the user to let svn know before
they're
starting to edit a file, so we can create a pristine off the
on-disk
file. This way we won't have pristineless modifi
Daniel Shahaf wrote:
> Daniel Shahaf commented on SVN-4884:
>
> Done in r1898739.
(Added the WC format and version to `svn info`'s other output modes.)
Great! Thanks, Daniel.
By the way, I see you cherry-picked a commit from trunk as the commit
before this fi
Nathan Hartman wrote:
> Suggestion: The user provides the earliest SVN version with which they
> want compatibility, and SVN picks the latest WC format version that is
> compatible with it. [...]
And Daniel Sahlberg wrote:
>> Regarding how to handle --wc-format-version=1.9, I'm leaning towards
>>
Karl Fogel wrote:
> Might it be better to put that file on the branch, [...]
Yes, sure; I'm not really sure why I didn't.
There, r1898819, in 'notes/i525/i525-user-guide.md'.
- Julian
Den ons 9 mars 2022 kl 20:53 skrev Julian Foad :
> This is why I think we should do at least one of:
>
> - require the exact first-introduced version (1.8 or 1.15)
> - rename the option to use a less ambiguous language, to something like
> '--wc-format-version=1.8' (meaning the version in which th
6 matches
Mail list logo
