Daniel Shahaf wrote:
>Lorenz wrote on Thu, Feb 23, 2017 at 07:33:54 +:
>[...]
>>
>> 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 subpa
Lorenz wrote on Thu, Feb 23, 2017 at 07:33:54 +:
> Daniel Shahaf wrote:
> >Lorenz wrote on Wed, Feb 22, 2017 at 15:28:19 +:
> >> 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 di
Branko ?ibej wrote:
>On 22.02.2017 17:42, Daniel Shahaf wrote:
>> Lorenz wrote on Wed, Feb 22, 2017 at 15:28:19 +:
>>> 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 ext
Branko Čibej wrote on Thu, Feb 23, 2017 at 13:47:12 +0100:
> On 22.02.2017 17:42, Daniel Shahaf wrote:
> > Lorenz wrote on Wed, Feb 22, 2017 at 15:28:19 +:
> >> Stefan Sperling wrote:
> >> >From 'svn help ps':
> >>> The URL may be a full URL or a relative URL starting with one of:
> >>>
On 22.02.2017 17:42, Daniel Shahaf wrote:
> Lorenz wrote on Wed, Feb 22, 2017 at 15:28:19 +:
>> 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
>>>
Daniel Shahaf wrote:
>Lorenz wrote on Wed, Feb 22, 2017 at 15:28:19 +:
>> 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 reposit
Lorenz wrote on Wed, Feb 22, 2017 at 15:28:19 +:
> 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
Stefan Sperling wrote:
>On Wed, Feb 22, 2017 at 03:12:55PM +0100, Harald Kirsch wrote:
>> Am 21.02.2017 um 15:40 schrieb Lorenz:
>> > And why not use "^^/" to denote working copy root relative?
>>
>> Would work for me. But intuitively ^^/ seems to refer even higher up in the
>> directory hierarch
On Wed, Feb 22, 2017 at 03:12:55PM +0100, Harald Kirsch wrote:
> Am 21.02.2017 um 15:40 schrieb Lorenz:
> > And why not use "^^/" to denote working copy root relative?
> >
>
> Would work for me. But intuitively ^^/ seems to refer even higher up in the
> directory hierarchy than ^/, but its not, s
Am 21.02.2017 um 15:40 schrieb Lorenz:
Harald Kirsch wrote:
[about working copy relative URLs]
This a purely client side path to URL transformation.
So what is needed as a means to tell the client to use the URL
associated with the given path.
there is already the "^/" notation to tell the
Harald Kirsch wrote:
>[about working copy relative URLs]
This a purely client side path to URL transformation.
So what is needed as a means to tell the client to use the URL
associated with the given path.
there is already the "^/" notation to tell the command line client
that you what to start a
Hi all,
as suggested by Johan, I dare to drop a feature suggestion onto this
mailing list.
In a multi project repository, ^/trunk and ^/branches do not usually
point to the trunk and branches of a project. Rather something like
^/somedir/someproject/branches
is needed.
Given a working c
12 matches
Mail list logo
