On 8/26/05, Flanakin Michael C Ctr HQ OSSG/OMR
<Michael.Flanakin@gunter.af.mil> 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?
>
> Michael
>
Typically you only check out the trunk, but if you need to do this for
your workflow you can svn remove the branches once they are no longer
active. They will still be in the repository, but you'll have to access them
by specifying a revision number in which they existed.
Or you can do non-recursive checkouts (-N), but this has problems
when doing operations in the directory that was checked out (but not
in any of it's fully checked out children).
Josh
---------------------------------------------------------------------
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:16:55 2005