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

Re: CVS & Subversion evaluation

From: Jack Repenning <jrepenning_at_collab.net>
Date: 2004-02-25 19:32:57 CET

On Feb 19, 2004, at 8:14 PM, Jesse Tilly wrote:

> In CVS, I would non-recursively update projectA, telling CVS to
> "create missing directories". I get projectA/tools and projectA/src. I
> go into src (where I suspect the config code is). Update again
> (non-recursive, create dirs) and projectA/src/config shows up. I go
> into
> that dir and update it all proper-like.
> Again, I'm doing it this way becuase don't want everything in the
> repository (for whatever reason...it doesn't matter here).
> A key note that at no time did I need to know any dir name aside from
> the root module. I'm letting CVS create the directories for me as
> needed.

As you say, SVN doesn't do this precise thing. But I think there's
another way to approach the problem you might try.

The value of the CVS non-recursive checkout here is in informing you of
what other directories exist at this level. With SVN, there's an "ls"
command that will tell you that (when directed at the repository URL).
You can use that to see the list of directories at the next level:
where presently you use "cvs co -R." plus "ls" (or maybe just watch the
scroll-by), you would now use "svn ls" alone. Having picked a tasty
candidate directory, you would "svn co" it, just as you now "cvs co"
it, to get the real files.

It's definitely a different model, but not so very different.

Jack Repenning
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
o: 650.228.2562
c: 408.835.8090

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 25 19:32:27 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.