feature suggestion: adressing the repo relative to working copy url

[Harald Kirsch]

Hi all,

there is the '^' notation to denote the repository root URL. In a
setting where many projects are hosted in one repository, however,
"^/branches" does not end up in a project's branches. Rather something like

^/somedir/someproject/branches

is needed.

Assuming I have a working copy of ^/somedir/someproject/trunk, it would
be great to address the repository relative to that URL. Say '%' would
be the shortcut, then I could

svn list %/../branches
svn copy . %/../branches/mycoolfeature
svn switch . %/../branches/mycoolfeature

Use of '..' seems to be forbidden in repository URLs, but some syntax
should be possible to address this.

Is this a feature request to put in Jira? Or is this actually possible
already and I just could not find it?

Harald.

[Johan Corveleyn]

On Sun, Feb 19, 2017 at 12:06 PM, Harald Kirsch

Post by Harald Kirsch
Hi all,
there is the '^' notation to denote the repository root URL. In a setting
where many projects are hosted in one repository, however, "^/branches" does
not end up in a project's branches. Rather something like
^/somedir/someproject/branches
is needed.
Assuming I have a working copy of ^/somedir/someproject/trunk, it would be
great to address the repository relative to that URL. Say '%' would be the
shortcut, then I could
svn list %/../branches
svn copy . %/../branches/mycoolfeature
svn switch . %/../branches/mycoolfeature
Use of '..' seems to be forbidden in repository URLs, but some syntax should
be possible to address this.
Is this a feature request to put in Jira? Or is this actually possible
already and I just could not find it?

Sounds like an interesting idea (not sure about the exact syntax, but
that can be worked out later). I think it would be useful to have a
shorthand for "url corresponding to the working copy root", and being
able to get at least siblings of that (using '..', or through some
other special syntax).

I don't think this is already a requested feature in JIRA, so please
go ahead and do so, so this doesn't get forgotten. But as a second
step I would suggest you start a discussion about this on the dev@
list (these issues usually don't implement themselves, so it helps if
someone at least drives the discussion about what the feature should
look like). I suppose other devs might come with all kinds of
considerations ... it could be tricky to do well.