Daniel Shahaf wrote: >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 >[...]
the last is an independent idea for an additional feature, right? 'foo' would be a shortcut for a base URL? I think, without some sort of indicator, it looks to much like a path. I would prefer to mark a shortcut explicitly as such. No idea how though, another prefix? Perhaps '^:shortcut/" would do? But back to original topic: I could live with using '^./' as the general prefix for "current working copy folder relative addressing". so my 4 examples above would change to: ^./subpath subpath of the current working copy folder ^./../ parent ^./../path sibling ^./../../ grand parent -- Lorenz
