Oh, sorry. Seems I had this completely wrong. I should have read the
original post more thoroughly. Please ignore my svnsync suggestion.

My apologies. :-)

:Darren.

On Tue, Mar 2, 2010 at 9:35 PM, Ben Collins-Sussman <[email protected]>wrote:

> svnsync has nothing to do with this;  that's a way of sucking out the
> *entire repository* to local disk.  Totally irrelevant to the problem
> at hand.
>
> Working copies are "glued" to their original repositories in multiple
> secret ways:  the original checkout URL is embedded deep within every
> secret .svn/ metadata directory in every folder.  So is the original
> repository UUID.  You shouldn't be trying to fool with this buried
> data;  it's just going to break stuff.
>
> The best possible thing to do is do a *fresh* checkout of the new
> repository into a totally new working copy.  Then run 'svn diff >
> mypatch' within your old working copy.  Then apply the patch to the
> new working copy and commit.  Then throw away the old working copy.
>
> If you're on windows and don't know how to do diff/patch, things are
> harder.  You can just copy the modified files over from the old to the
> new working copy.  Or use the diff/patch tools supplied with
> TortoiseSVN.
>
>
>
>
> On Tue, Mar 2, 2010 at 2:41 PM, Dr Dave <[email protected]> wrote:
> > :
> >> Sounds to me like it might be simpler to svnsync from Google Code to
> your
> >> local harddisk and then svnsync back up to Google Code in the new
> project.
> >
> > I'm using TortoiseSVN on Windows XP.  There is nothing in Tortoise
> > that I can find to do an "svnsync" or "replicate repository".  I
> > already have a copy of the old repository on my local harddisk (my
> > working copy).  I just need to Relocate, Switch, Export, or SVNsync to
> > the new repository.  Relocate almost worked, except for the problem
> > with my UUID.
> >
> > -- Dave
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> "Project Hosting on Google Code" group.
> > To post to this group, send email to
> [email protected].
> > To unsubscribe from this group, send email to
> [email protected]<google-code-hosting%[email protected]>
> .
> > For more options, visit this group at
> http://groups.google.com/group/google-code-hosting?hl=en.
> >
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Hosting on Google Code" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<google-code-hosting%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/google-code-hosting?hl=en.
>
>


-- 
----------------------------------------------------------------------
 :Darren :Pearce-Lazard
----------------------------------------------------------------------
 *** Shop & Donate: http://buy.at/campuskids ***
----------------------------------------------------------------------
 [email protected]
 Postdoctoral Researcher
 London Knowledge Lab, University of London
----------------------------------------------------------------------
 [email protected]
 Visiting Research Fellow
 Informatics, University of Sussex
 http://www.informatics.sussex.ac.uk/users/darrenp/
----------------------------------------------------------------------
 [email protected]
 http://www.linkedin.com/in/darrenpearce
----------------------------------------------------------------------

-- 
You received this message because you are subscribed to the Google Groups 
"Project Hosting on Google Code" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-code-hosting?hl=en.

Reply via email to