Re: [jcvs] Checkout semantics.

[Tim Endres <time@trustice.com>]

Essentially, you enter the path of the module you wish to checkout. However,
I believe there is still a bug (which I thought I had fixed) that causes the
newer CVS/Entries to overwrite the old, as opposed to appending. I intend to
release 5.3.2 which will hopefully (re)fix this bug, as well as a few others
introduced in 5.3.1.
tim.

> Hi,
> 
> I'm afraid I have more questions or comments.
> 
> Lets say that I have a module in a repository whose top-level directory 
> is called "Module".  It has subdirectories "A", "B", and "C".  I want to 
> checkout A and C, but not B.  Thus, I want my sandbox to look like this:
> 
> Module/A
> Module/C
> Module/CVS
> 
> with Module/CVS/Entries listing A and C as directories.
> 
> My current situation is actually more complicated than this.  I 
> currently have six subdirectories and one file in the Module directory, 
> all of which were checked out with jCVS.  And yet, my top-level Entries 
> file only lists *two* of the six directories and does not list the file 
> at all.
> 
> What is the proper way to checkout subsets of module directories with 
> jCVS?    What are the semantics of the checkout command?
> 
> Thanks,
> Joe
> 
> --------------------------------------------------------------------
> View List Archive:   <http://www.gjt.org/mlist/jcvs/threads.html>
> Search List Archive: <http://csdl.ics.hawaii.edu:8100/>
> To unsubscribe from this list:
>    <http://www.gjt.org/servlets/MailingLists/UnsubForm.html/jcvs>
>