removing old branches

[Joey Hess <jo...@kitenet.net>]

Does it make sense to svn rm an old branch after it's merged back to the
trunk, or not? I'm thinking about doing that so only active branches are
present in my project's branches/ directory. Of course the old branch
would still be available if you knew the revision before it was deleted.
Or I could make an branches/attic directory and move it under there. Has
any best practice been developed in this area yet?

Also, does can svn switch work on a subdirectory of a WC, or only on the
whole WC?

-- 
see shy jo

Re: removing old branches

[Garrett Rooney <ro...@electricjellyfish.net>]

Joey Hess wrote:
> Does it make sense to svn rm an old branch after it's merged back to the
> trunk, or not? I'm thinking about doing that so only active branches are
> present in my project's branches/ directory. Of course the old branch
> would still be available if you knew the revision before it was deleted.
> Or I could make an branches/attic directory and move it under there. Has
> any best practice been developed in this area yet?

The Subversion developers tend to do that in our own repository.  It's 
nice to be able to see what branches are actually in use just by looking 
at the branches/ directory in HEAD, and as you say, you can always go 
back to the old versions if you so desire.

> Also, does can svn switch work on a subdirectory of a WC, or only on the
> whole WC?

Each subdirectory is essentially it's own WC, so yes, it will.  You can 
even take switch further though, and switch a single file if you so 
desire.  We often use the pattern of switching a single subdirectory 
when we have a branch that is only making changes to one of Subversion's 
libraries.  You branch from trunk, then switch only the subdirectory 
you're modifying over to the branch.  This way you keep your 
modifications on the branch, but can easily pick up everyone else's 
changes from trunk without having to merge them all over.  Of course you 
still need to be careful about merging modifications to the subdirectory 
you've switched to the branch, but you'd have to do that anyway.

-garrett



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: removing old branches

[cm...@collab.net]

Joey Hess <jo...@kitenet.net> writes:

> Does it make sense to svn rm an old branch after it's merged back to the
> trunk, or not? I'm thinking about doing that so only active branches are
> present in my project's branches/ directory. Of course the old branch
> would still be available if you knew the revision before it was deleted.
> Or I could make an branches/attic directory and move it under there. Has
> any best practice been developed in this area yet?

It's up to you.  I like to remove the dead branches because I like to
'ls branches' to see what lines of side development are going at any
given time.  I don't know if we've been doing this long enough to
develop best practices -- perhaps others have thoughts on this?

> Also, does can svn switch work on a subdirectory of a WC, or only on the
> whole WC?

You can switch a single file or subdir or a whole tree.  It doesn't
matter.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org