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

Re: Making a branch

From: Martin Scharrer <mailinglists_at_madmarty.de>
Date: 2006-12-22 10:47:35 CET

On Tuesday 19 December 2006 15:38, Steve.Nelson@uk.delarue.com wrote:
> I have a repo set up as follows:
>
> /devrep/trunk - contains several hundred individual programs
> /devrep/branches - contains directories for trouble tickets requesting
> changes to trunk, which are merged back into trunk when finished

> What's the best way to do this? I don't want every developer to have to
> have a complete copy of the whole repo, but it seems I can't do a remote
> creation of a branch without a working copy.
>
> What would the procedure be to create the subdirectory and move the
> files over?
1) You check out a non-recursive copy of /devrep/branches (i.e. only the dir
itself without subdirs)
        $ svn co -N <url of /devrep/branches> branches
        $ cd branches
2) Create your new branch dir
        $ svn mkdir <new branch name>
        $ cd <new branch name>
3) Copy the files you need over using the url form
        $ svn copy <url of #1 file> .
        $ svn copy <url of #2 file> .
        $ svn copy <url of #3 file> .
        $ svn copy <url of #4 file> .
        ...
        ...
4) Check the whole thing in
        $ cd ..
        $ svn ci <new branch name>

So far I know the newest develop revision of subversion supports now multiple
copy actions with one command, so step 3 could be easier in the future.

And Steve, could you please configure your E-mail software to produce the
standard 'In-Reply-To:' header. You replies always destroy the thread
display on my side.

best,
Martin

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 22 10:49:52 2006

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.