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

RE: Branching and URL-encoding

From: Oddvar Kloster <Oddvar.Kloster_at_sintef.no>
Date: Mon, 14 Nov 2016 08:50:25 +0000

I tried to branch to "branches/Branch at 20%cake".
(It was visible in the first line of img2.png. Sorry if that was a bit cryptic.)
In the Copy to scenario, I chose "branches/Branch with space and 25%cake".

Oddvar

> -----Original Message-----
> From: Stefan Kueng [mailto:tortoisesvn_at_gmail.com]
> Sent: 11. november 2016 18:41
> To: dev
> Cc: Oddvar Kloster
> Subject: Re: Branching and URL-encoding
>
>
>
> On 11.11.2016 14:19, Oddvar Kloster wrote:
> > Hi,
> >
> >
> >
> > In the branch/tag dialog, the source URL is displayed in URL encoded
> > form. This causes paths that contain spaces to become unreadable. See
> > img.png.
>
> Ok, that's bad. Will fix that.
>
> > If you edit the path and commit, the path is URL-decoded at some
> > point, converting %20's back into spaces. However, this can have
> > unpleasant consequences if you actually want the branch name to contain
> %-symbols.
> > See img2.png for an example.
>
> how did you do that? I've tried with different urls/paths and could not get
> such an error.
>
> > I also tried performing the same branching using 'Copy to...' from the
> > repo browser. This exhibits the same problem – see img3.png.
>
> could not get the error here either, tried different urls/paths.
> Can you tell me what you've entered here?
>
> Stefan
>
> --
> ___
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest interface to (Sub)version control
> /_/ \_\ http://tortoisesvn.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3193757

To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].

img2.png
Received on 2016-11-14 13:47:58 CET

This is an archived mail posted to the TortoiseSVN Dev mailing list.

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