All, There's been some debate and confusion about the correct command to use for switching llvm-gcc-4-2 to llvm-gcc-4.2. Despite previous claims, --relocate is the wrong thing.
So, there are three cases: 0. You have never checked out llvm-gcc-4-2 1. You have no changes in your llvm-gcc-4-2 working copy that are yet to be committed. 2. You have changes in your llvm-gcc-4-2 working copy that you need to commit. For CASE 0: Do nothing. Ignore this email. For CASE 1: cd /to/directory/above/llvm-gcc-4-2 rm -rf llvm-gcc-4-2 svn co https://[EMAIL PROTECTED]/svn/llvm-project/llvm-gcc-4.2/trunk llvm-gcc-4.2 For CASE 2: cd llvm-gcc-4-2 svn switch https://[EMAIL PROTECTED]/svn/llvm-project/llvm-gcc-4.2/trunk . cd .. mv llvm-gcc-4-2 llvm-gcc-4.2 Of course, replace "uname" with your user name in the URL portion of the svn commands above. *Many thanks to Duncan Sands for helping to figure this out. Reid. On Tue, 2007-07-17 at 11:11 +0200, Duncan Sands wrote: > On Tuesday 17 July 2007 09:32:28 Reid Spencer wrote: > > P.S. > > You want the svn switch --relocate option > > After some fiddling I could persuade svn switch to do something - > not sure what it was doing but it sure caused a lot of disk usage :) > But I failed to get it to update my working copy correctly, i.e. > svn update would still barf. In the end I just checked out a new > copy... If anyone knows exactly how I should have used svn switch > I'd be interested to know. > > Ciao, > > Duncan. _______________________________________________ llvm-commits mailing list llvm-commits@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
