Rodent of Unusual Size wrote:
>
> Maybe I'm missing something (probably), but is there any way
> to persuade 'cvs update' to pick up new directories that have
> been added to the module? The only way I've been able to
> get them is with a checkout, which hasd other problems..
>
> One of the modules I regularly update actually pulls in a couple
> of aliased module. The entry in CVSROOT/modules is something like
> this:
>
> bar bar
> foo foo &foo-1 &foo-2
> foo-1 -d foo1 bar-module/foo1
> foo-2 -d foo2 bar-module/foo2
>
> So when I check out foo, I get subdirectories foo1/ and foo2/
> from the bar module. All's well so far.
>
> However, when I try to use 'cvs checkout' to update my local foo
> working directory, I get conflicts for all the files in the
> foo1/ and foo/2 subdirectories.
>
> A workaround would be to only use checkout to create a new working
> directory, and use 'cvs update' if it already exists -- except I
> don't see a way to get 'cvs update' to pick up new sibdirectories.
>
> Any thoughts? TIA..
`cvs update -d` (from `cvs -H update`). another flag for update that I've found
handy is "-P".
