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

Re: Dropping Subversion

From: Ben Reser <ben_at_reser.org>
Date: 2004-04-03 02:20:13 CEST

On Sat, Apr 03, 2004 at 01:50:41AM +0200, Marcin Kasperski wrote:
> ... and spend some nice time removing unnecessarily checked out files

How long does it take to delete a directory and its contents? You
wouldn't even have to recheck the files out:

svn co https://svn/project


mv project/trunk project-trunk
rm -rf project
mv project-trunk project

> How do you check out next fresh working copy?

svn co https://svn/project/trunk project

>Do you check out each module separately?


> What about updating?

svn up

You do realize you can nest a working copy within another working copy?
You'll have to run your updates separately but if they're separte
projects isn't that what you want anyway?

If you want to switch to a different branch or tag, you can use svn

It's all a heck of a lot easier than you make it out to be.

> Maybe. But seems to me, it would be more natural NOT to checkout all the
> tags by default and give -I_know_what_I_am_doing switch for those rare
> cases where someone really wants to do that.

subversion doesn't know what a tag is. How you use a path in your repo
is what matters. In order to get what you want here would force us to
force everyone into a set of repository layouts or make the design more
complex for something that frankly isn't really much of a problem.

Ben Reser <ben@reser.org>
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 3 02:20:28 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.