On Mon, 14 Feb 2022 at 01:39, Karl Fogel wrote:
> On 12 Feb 2022, Mark Phippard wrote:
> >Just to offer a counterpoint Karl, I always assumed the goal of
> >the
> >branch was to have no pristines in the WC and the "on-demand"
> >aspect
> >was referring to an internal SVN detail that it would have
On Mon, Feb 14, 2022 at 11:13 AM Ivan Zhakov wrote:
> On Mon, 14 Feb 2022 at 01:39, Karl Fogel wrote:
>> On 12 Feb 2022, Mark Phippard wrote:
...
>> In any case, the branch name doesn't matter too much here,
>> especially since it's going to get merged soon. However, for the
>> user-facing name
Karl, thanks for bringing a user-focused perspective to the naming. In
Subversion's UI we will not necessarily expose any name for the feature,
but we might, e.g. in a configuration file or in help text. In
describing what's new in 1.15 people will certainly start using some
short name for the feat
Karl Fogel wrote:
> Julian, just FYI I committed r1898020 to update the
> 'BRANCH-README' file on the new 'pristines-on-demand-on-mwf'
> branch. [...]
Thanks for the heads-up. That's a useful clarification of the combined
README's on the combined branch.
- Julian
On Mon, Feb 14, 2022 at 6:07 AM Julian Foad wrote:
> Ideas:
>
> - "Option to optimize a checkout for minimal disk space rather than
> minimal network traffic."
>
> - "50% off. Unlimited offer. Buy it now. Shrink your checkouts to
> half the size.* (Small print: *Compared to our previous c
On 14 Feb 2022, Julian Foad wrote:
Karl, thanks for bringing a user-focused perspective to the
naming. In
Subversion's UI we will not necessarily expose any name for the
feature,
but we might, e.g. in a configuration file or in help text. In
describing what's new in 1.15 people will certainly s
6 matches
Mail list logo
