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

Trimmed branches (was: RE: Retroactively branching something / trimmed branches)

From: Roger Lipscombe <rogerl_at_1e.com>
Date: 2005-11-02 11:48:17 CET

> Depends on what you mean. Do you mean: You have a trunk, and you have
> continued to develop on the trunk, but now you want to have a branch
> that's based on an earlier version of trunk?

Yes, that's exactly what I meant.

> If so, then you can simply copy that earlier trunk:
> svn cp -r 1234 -m "Making Foo-3.0 branch from trunk r1234" \
> $REPO/trunk \
> $REPO/branches/Foo-3.0


> So you are using this layout:
> /repo/
> trunk/
> lib/
> project1/
> project2/
> branches/
> foo-branch/
> lib/
> project1/
> project2/

Yep. All of the products depend on the same set of libraries, so I'd
rather not use the alternative layout, which (as far as I can tell)
requires that each project know which branch it's in in order to get to
the shared libraries.

My second question is more that I'd like to have something like this
(ignoring tags):


That is: when I branch 'project1', I'd like to prune the tree so that
the project1 branch only contains the stuff needed for project1, and the
project2 branch only contains the stuff needed for project2.

Essentially, this is for security purposes -- if we lock down the repos
by project in future, we don't necessarily want someone to get hold of
an earlier copy of a project by snaffling it out of another project's

Should I simply do the copy, and then delete the unneeded stuff from the
branch, or can I build the branch in a piece-meal fashion in a WC before
committing it?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 2 11:50:18 2005

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.