On Tue, Feb 5, 2013 at 10:43 AM, Bert Huijben <b...@qqmail.nl> wrote: > svn can do an an auto-relocate after user confirmation... But relocates are > for when a repository moves, not when something moves inside a repository. > (See svn_client_update_internal()) > > This is all inside a repository... so we are talking about an update that > should perform a switch help a user'... But we can’t break history, or > switching between old or future revisions.
So, aren't we actually talking then about a new feature "make update able to follow moves of wc root"? Wouldn't that solve the problem for the ASF (no redirects etc. involved)? I've been bitten by this a couple of times myself: if ^/trunk/projectBleedingEdge gets renamed to ^/trunk/projectBoring, all users that have a checkout of ^/trunk/projectBleedingEdge will receive an error upon 'update', and will have to switch. OTOH, the odd user that has the entire ^/trunk checked out has no problem, because projectBleedingEdge is just a subdir which can be moved automatically by 'update'. Wouldn't it be nice if 'update' could move (or switch) the entire working copy automatically if the wc root gets renamed / moved? Or a parent of the wc root? Not saying that this is easy or that I have something significant to contribute, just ... it would be nice :-). -- Johan
