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

Re: Feature Suggestion: Ability to specify dedicate path for .SVN folders.

From: Ryan Schmidt <subversion-2005_at_ryandesign.com>
Date: 2005-09-19 03:07:55 CEST

> On Sep 17, 2005, at 11:32, Ryan Schmidt wrote:
>> I always have a working copy of trunk (or sometimes 2 or 3, if I'm
>> working on 2 or 3 tasks at once), and another working copy of the
>> latest released branch, which I can merge my trunk changes into if
>> desired. When that release branch goes obsolete and a new release
>> branch starts being used, I svn switch my branch working copy to
>> the new release branch.

On Sep 19, 2005, at 02:36, Paul Coddington wrote:

> However, I can see that you could go either way, and certainly
> having "trunk" and "branches" in your working copy (as you suggest)
> saves switching and makes check outs a single click process, and
> having the working copy tree and repository tree identical would be
> conceptually simpler for the 'newbies' on the team.

To be clear: I don't have trunk and branches in my working copy;
rather I have a local folder for the project (which I made manually
in the filesystem), and in that, I have two separate working copies,
one of the trunk, and one of the current release branch. So my local
directory structure does not mirror the repository's -- my local
structure doesn't have a directory "branches"; I only have one branch
that I need to have checked out. Conversely, I may have multiple
working copies of trunk, since I may be working on more than one
thing, whereas the repository obviously only has a single trunk.

One of the newbies on our team did exactly what you say, and checked
out the project root from the repository, thereby receiving the
trunk, a full copy of every branch, and a full copy of every tag. I
scolded him for wasting disk space and making the server and network
slow while it figured all that out (and for telling the next newbie
to do it that way), and told him to just use working copies of what
he needed in the future, because I'm pretty sure that's better.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 19 03:09:39 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.