Lorenz wrote on Wed, Feb 22, 2017 at 15:28:19 +0000:
> Stefan Sperling wrote:
> >From 'svn help ps':
> > The URL may be a full URL or a relative URL starting with one of:
> > ../ to the parent directory of the extracted external
> > ^/ to the repository root
> > / to the server root
> > // to the URL scheme
> > ^/../ to a sibling repository beneath the same SVNParentPath location
>
> I am aware of the svn:externals syntax, but in light of the fact that
> ^/ was alread adopted, I thought it best to stick with the ^
>
> If the cmomand line client accepts the ^ as the "translate the
> following path to an URL" marker, then anything after it could be
> interpreted as a normal path.
>
> ^/ repo root relative
> ^/../name sibling repo
>
> ^subpath subpath of the current working copy folder
> ^../ parent
> ^../path sibling
> ^../../ grand parent
If the first of these four were changed to require a ./ path component,
we could repurpose the ^foo/ syntax to something else:
^./subpath subpath relative to URL of cwd
^foo/ as defined by a --config-option=config:short-urls:foo=bar
config option
> and so on
>
> The only difference to the svn:externals syntax you need to keep in
> mind is that on the command line you always need the ^ in front.
>
>
> I think my proposal for using ^^/ as working copy root is not
> absolutely neccessary, by the way.
> You can always get there with the appropriate number of ../ 8-)
The working copy root is a fluid concept: sometimes people root their
wc's above or below the branch root. It might be nice to have a syntax
that will mean "relative to the branch root"... that is, to have the
design specify a syntax that will mean "relative to the branch root"
when we invent a concept of "branch roots".
Cheers,
Daniel
