On 15 Feb 2022, Nathan Hartman wrote:
Possibly bikeshedding a bit, but this seems to return to the idea
of
"turning on" what we are (tentatively) calling "local
base"... IMHO it
would be better if it were reversed to "--remote-base=yes" to
convey
that this is non-default and opt-in. (Or possib
On 15 Feb 2022, Mark Phippard wrote:
On Tue, Feb 15, 2022 at 12:00 PM Julian Foad
wrote:
Currently: "svn checkout --compatible-version=1.15". No feature
name
involved. Not saying that's good, just that's the current
state.
Are you saying this is how you would activate this no-pristines
featu
On Tue, Feb 15, 2022 at 2:22 PM Karl Fogel wrote:
> As a command-line option for per-WC behavior, it might be
> something like this on checkout:
>
> --local-base=no
>
> When the option is not provided, the default would be "yes" of
> course (in a sense, it's been defaulting to "yes" for decades
On Tue, Feb 15, 2022 at 12:00 PM Julian Foad wrote:
>
> Karl Fogel wrote:
> > [...] there has to be some way for the user to specify at checkout
> > time [...]
>
> Currently: "svn checkout --compatible-version=1.15". No feature name
> involved. Not saying that's good, just that's the current state
TL;DR: OK to merge multi-wc-format to trunk soon?
Having worked with it these last few weeks, I think the essential pieces
are in place for multi-wc-format to be merged to trunk.
I am still working on the last pieces of pristines-on-demand rebased on
top of this branch: fixing tests to work prope
On 15 Feb 2022, Nathan Hartman wrote:
How about:
Remote BASE
(as opposed to Local BASE).
The idea here being that BASE is a concept with which users
should be
familiar, while pristines are part of Subversion's implementation
under the hood.
Getting closer, I think! "base" seems like a goo
Karl Fogel wrote:
> [...] there has to be some way for the user to specify at checkout
> time [...]
Currently: "svn checkout --compatible-version=1.15". No feature name
involved. Not saying that's good, just that's the current state.
> [...] Those are *descriptions* [...]
Yes; hoping to inspire
On Mon, Feb 14, 2022 at 4:54 PM Karl Fogel wrote:
>
> ROTFL :-). I'll take #2 with a side of onion rings, please.
>
> Those are *descriptions*, for the release notes and other
> documentation, but we will still need a *name* too, to use in the
> command-line flag (or config option, whatever).
Hi Stefan,
thank you very much for your detailed answer!
Your explanations very much make sense to me. I understand that a
universal solution for all types of externals is difficult or maybe even
impossible.
Probably my point of view on svn:externals is a bit different, because
we quite oft
9 matches
Mail list logo
