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

Re: Old Branches

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-08-26 23:09:35 CEST

On Aug 26, 2005, at 3:46 PM, Flanakin Michael C Ctr HQ OSSG/OMR wrote:

> My team is branching per release. Once code is moved to the testing
> environment, it is branched. Bugs are fixed within the branch and the
> branch is tagged with the official release. Bugs found in
> production are
> again fixed in the branch and a new tag is created for the re-release.
> My question is: With this method, a lot of branches and tags are
> created; is there a way to allow users to decide whether or not
> they are
> downloaded to the local machine or archive them so they aren't
> implicitly retrieved? Obviously, they can be deleted from a user's
> machine; but if the user decides to update the root, the directories
> will come back. This could eat up user resources pretty fast. Does
> anyone know of a way around this problem?

(You should send mails like this to the users@ list, it's not
actually about developing subversion code.)

Why would users checkout the 'root' of a project at all? The
standard thing to do is checkout *one* copy of the tree: usually the
'trunk'. Then you can 'svn switch' the working copy to any
particular branch or tag as needed.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 26 23:11:29 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.