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

[PATCH] issue #2505: Add FAQ entry: Why doesn't svn switch work in some cases?

From: James Coleman <jamesc_at_dspsrv.com>
Date: 2007-07-13 17:16:32 CEST


I'd like to submit a patch to the svn faq.
First patch submit (first post to dev!) so please forgive me if I'm making mistakes.
See attached add_svn_switch_issue_2505_to_faq.patch
For your convenience there is a copy of the patched faq.html here:

Add entry in FAQ for issue #2505: Why doesn't svn switch work in some cases?

* www/faq.html
Add svn switch question to index and add FAQ entry at end of Troubleshooting section.

Attached patch contains:

1. FAQ entry in Troubleshooting (index entry and FAQ entry)
    Why doesn't svn switch work in some cases?
    Summary of problem and how to avoid the problem.
    Examples of problem with errors seen and how to recover from the situation.

2. Two other tiny errors in faq (internal links):
    entry in FAQ TOC for #broken-subclipse was missing (nxt to new svn switch entry).
    and found a href to #moderated that should be #moderation
    I'm VERY sorry for including them in this patch but they really are tiny! :-7

More details on the problem:

We encountered problems using svn switch.
If there are unversioned items in working copy and they have a history on branch being
switched to then the svn switch will stop with an error. User is left with a half-switched
working copy. This is the issue:


The very workable solution is to have a rule to only switch from a
''pristine'' clean working copy.

I asked about this svn switch issue on svn users and it does seem
that a couple of people know about this. More info on the users
list here:


It is a bit troublesome when users first encounter it and there is very
little info to be found about it. I think that especially larger projects
with lots of parallel development and branches would benefit from having
this documented.

Now, apart from the FAQ entry after testing this more, I am thinking the
issue might be always recoverable from by removing any unversioned files
and continuing with the switch. I added 2 recipies to 2505 and summarised
what I think might be a solution.

Of course there might be a nastier issue buried here but I'm thinking
now that there isn't and this is just a user problem.

Thanks people,


Thanks to people who replied on users list and bug 2505 especially Karl Fogel. :)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 13 17:15:35 2007

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.