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

RE: Is there a clean way to move a-project to a-project/trunk

From: Cooke, Mark <mark.cooke_at_siemens.com>
Date: Wed, 29 Sep 2010 10:50:06 +0100

> -----Original Message-----
> From: Tino Schwarze [mailto:subversion.lists_at_tisc.de]
> Sent: 29 September 2010 09:14
> To: users_at_subversion.apache.org
> Subject: Re: Is there a clean way to move a-project to a-project/trunk
>
> On Wed, Sep 29, 2010 at 03:32:07PM +0800, Rice Yeh wrote:
>
> > I am trying to separate my project a-project into
> > a-project/trunk and a-project/branches. First, I like to
> > move a-project to a-project/trunk. But this is not allowed
> > since trunk is inside a-project. I might first move
> > a-project to tmp and then move tmp to a-project/trunk. But
> > the tmp directory is created in repository and this seems
> > not elegant. Is there a clean way to do this?
>
> You could try using svnmucc and performing all these moves in one
> operation(=commit). Then you'll have the tmp directory as
> well but only
> hidden within that one revision. (I didn't try it though, not sure
> whether it would work.)
>
Why not just get a working copy, do your changes and then commit? No
need for a temp directory, just create new "trunk/", move all the files
and subfolders to the new dir (using svn tools of course), then commit.

Or am I missing something obvious? Should keep all history, only one
commit, no tmp directory. Simples?

~ mark c
Received on 2010-09-29 11:50:52 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.