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

Re: Selectively checking out and working on subprojects?

From: Junio C Hamano <junkio_at_cox.net>
Date: 2004-02-06 01:52:31 CET

>>>>> "SF" == Seth Falcon <sfalcon@fhcrc.org> writes:

SF> Ok, so maybe I'm not understanding your problem, but why not checkout
SF> one "project" at a time.

SF> So instead of
SF> $ svn co $R/pub
SF> Use:
SF> $ svn co $R/pub/kernel
SF> $ svn co $R/pub/tex
SF> etc.

Thanks for your comments. But I would imagine "svn ls" or "svn
st" in the working directory you checked out kernel and tex into
would not show what other trees are under pub/. When my working
directory is disconnected (e.g. laptop on the road), being able
to find out names of existing directories sometimes help
(admittedly only sometimes).

This I admit is a minor annoyance, but it seems to me that "svn
co -N", if worked properly, would be a perfect way to resolve
this annoyance. Stated stronger, if it fails to do that, I do
not see what the point of "svn co -N" is.

Interestingly, "svn add" takes -N and works as expected:

    $ mkdir pub pub/kernel pub/tex pub/junk
    $ svn add -N pub
    $ cd pub
    $ svn add kernel
    $ svn add tex
    $ cd ..
    $ svn commit -m 'Import stuff but not junk'

Adding "pub" nonrecursively does not *seal* that directory (you
can later add its subdirectories or files selectively).

However, "svn co -N" does not work like that; I feel that "svn
add" and "svn co" should behave symmetrically. As I wrote in my
previous post, the following fails when trying to check out or
update the subdirectory:

    $ svn co -N pub
    $ cd pub
    $ svn co kernel ;: svn up kernel does not work either.

When "svn co -N pub" checks out the "pub" directory, it seems to
*seal* that directory in such a way that later attempts to svn
co/up its subdirectory do not work there.

I would be very happy if "svn co -N" behaved as if a recursive
full checkout immediately followed by removal of all directory
contents were done. Should I maybe file a bug against "svn co

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 6 01:53:10 2004

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.