You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Colleen Dick <pl...@peak.org> on 2006/04/07 17:38:54 UTC
repair altering directories in working copy
One of my programmers checked out a new working copy but he screwed up
with the directory structure. We needed the code to be in directory x
but instead he checked out the more than we want. so under directory x
he had x/projname/trunk/codefiles.*
Rather than wiping it out and starting over, he simply moved everything
back in the file system a couple of dirs, so the structure now works
from the point of view of building the app. Then he did some work.
Then some other folks did some commits from other copies. When I do a
svn status it says . is not a working copy so I'm sure commit or update
won't work now. Is there some way I can tell svn what we did or
should I make him manually save his tweaks and start over with a proper
working copy? The move command in the redbean book seems to want to
change the structure in the repo which is not what I want. Thanks..
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: repair altering directories in working copy
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On 4/7/06, Colleen Dick <pl...@peak.org> wrote:
> Due to a problem the repository has been relocated to a different device
> Unfortunately the people who maintain the repository changed the path
> name. I can't simply rename the path on the svn server. How do I tell
> my working copy what the new pathname is?
svn switch --relocate $OLD_URL $NEW_URL
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: repair altering directories in working copy
Posted by Colleen Dick <pl...@peak.org>.
> ----- Original Message ----
> From: Colleen Dick <pl...@peak.org>
> To: users@subversion.tigris.org
> Sent: Friday, 7 April, 2006 2:38:54 PM
> Subject: repair altering directories in working copy
>
> One of my programmers checked out a new working copy but he screwed up
> with the directory structure. We needed the code to be in directory x
> but instead he checked out the more than we want. so under directory x
> he had x/projname/trunk/codefiles.*
> Rather than wiping it out and starting over, he simply moved everything
> back in the file system a couple of dirs, so the structure now works
> from the point of view of building the app. Then he did some work.
> Then some other folks did some commits from other copies. When I do a
> svn status it says . is not a working copy so I'm sure commit or update
> won't work now. Is there some way I can tell svn what we did or
> should I make him manually save his tweaks and start over with a proper
> working copy? The move command in the redbean book seems to want to
> change the structure in the repo which is not what I want. Thanks..
>
On Fri, 2006-04-07 at 12:36 -0700, Malheiro Luis wrote:
> I guess he copied only the files, not the whole directory. Probably your .svn sub-directory is missing in the x directory.
> Can you find out the exact revision he did checkout? If so, you can checkout that same revision to a new working copy and then copy his files over to it.
>
>
Due to a problem the repository has been relocated to a different device
Unfortunately the people who maintain the repository changed the path
name. I can't simply rename the path on the svn server. How do I tell
my working copy what the new pathname is?
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: repair altering directories in working copy
Posted by Malheiro Luis <lu...@yahoo.com>.
I guess he copied only the files, not the whole directory. Probably your .svn sub-directory is missing in the x directory.
Can you find out the exact revision he did checkout? If so, you can checkout that same revision to a new working copy and then copy his files over to it.
----- Original Message ----
From: Colleen Dick <pl...@peak.org>
To: users@subversion.tigris.org
Sent: Friday, 7 April, 2006 2:38:54 PM
Subject: repair altering directories in working copy
One of my programmers checked out a new working copy but he screwed up
with the directory structure. We needed the code to be in directory x
but instead he checked out the more than we want. so under directory x
he had x/projname/trunk/codefiles.*
Rather than wiping it out and starting over, he simply moved everything
back in the file system a couple of dirs, so the structure now works
from the point of view of building the app. Then he did some work.
Then some other folks did some commits from other copies. When I do a
svn status it says . is not a working copy so I'm sure commit or update
won't work now. Is there some way I can tell svn what we did or
should I make him manually save his tweaks and start over with a proper
working copy? The move command in the redbean book seems to want to
change the structure in the repo which is not what I want. Thanks..
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org