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

Re: Coniguring 301/302 redirects to track an fspath rename

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Sat, 2 Feb 2013 17:44:00 +0200

Branko Čibej wrote on Sat, Feb 02, 2013 at 11:20:05 +0100:
> On 01.02.2013 21:33, 'Daniel Shahaf' wrote:
> > Bert Huijben wrote on Fri, Feb 01, 2013 at 21:28:10 +0100:
> >> Why not just leave a top level folder with some readme?
> >>
> > Every time a podling graduates from the incubator, we do a rename:
> > svn mv ^/incubator/flex ^/flex
> >
> > If we can return 301 whenever somebody does 'svn up' in a wc of
> > ^/incubator/flex, we'll save many users (2-4 projects every month)
> > having to learn about 'svn relocate'.
>
> I'd have thought a proxy would be easier to set up, and more
> bullet-proof, since it wouldn't depend on magic happening in the client.
>

Thta doesn't solve the problem --- even if you did a transparent proxy
from /incubator/foo to /foo, you'd still have the problem of allowing
access to historical (pre-rename) revisions of /incubator/foo.

(unless the proxy is somehow peg-revision-aware and translates
'svn ls /incubator/foo_at_42' to 'svn ls -r42 /foo_at_HEAD'.)

> Sure, proxying eats more server resources than redirecting.
>
> -- Brane
>
> --
> Branko Čibej
> Director of Subversion | WANdisco | www.wandisco.com
>
Received on 2013-02-02 16:44:40 CET

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

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