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

Re: issue 919 solution

From: <junkio_at_cox.net>
Date: 2003-06-20 02:20:25 CEST

>>>>> "BS" == Ben Collins-Sussman <sussman@collab.net> writes:

BS> 'incomplete' != 'aborted'. Not at all! It means that the directory
BS> isn't 100% confident that it has a correct/complete list of entries.
BS> ...
BS> For example... this is how we do checkouts now: we create a root
BS> directory with a single entry for '.', mark it 'incomplete', and run
BS> 'svn update'. Has nothing to do with abortions or failures.

The "incomplete" route may also solve the asymmetric behaviour [*]
between "svn add -N" vs "svn co -N", I would presume. If that
is the case I would very much like it.

[*] Here is the asymmetry I am annoyed about.

When you are adding a tree with children, you could say:

    $ ls dir
    file1 little-subdirectory file3 huge-subdirectory
    $ svn add -N dir
    $ cd dir
    $ svn add file1 little-subdirectory
    $ cd ..
    $ svn commit dir

to selectively add to the set of things to be placed in the
repository. But checkout does not work that way nicely:

    $ svn co -N dir

would create dir, but it does not seem to know what hangs under
it, so the following after the above checkout would not give me
little-subdirectory nor file1.

    $ cd dir
    $ svn update

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 20 02:21:22 2003

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.