[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: feature suggestion: adressing the repo relative to working copy url

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Mon, 20 Feb 2017 20:22:33 +0100

On Sun, Feb 19, 2017 at 12:06 PM, Harald Kirsch
<harald.kirsch_at_raytion.com> wrote:
> 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.

-- 
Johan
Received on 2017-02-20 20:23:47 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.