[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 'cvs update' skipping directories

From: Russ Tremain
Subject: Re: 'cvs update' skipping directories
Date: Tue, 30 Jan 2001 14:07:08 -0800

At 1:11 PM -0800 1/30/01, Larry Jones wrote:
>Peter Schuller writes:
>> Basically, if I do a check-out I get everything. But if someome else then
>> adds a directory I sometimes (but not always) won't get a copy of that
>> directory when doing "cvs update".
>Update doesn't get new directories by default, you need to use the -d
>option.  (The reason is that CVS doesn't have any way to tell the
>difference between a newly added directory and an old one that you
>explicitly didn't checkout.)  If you want that behavior all the time,
>you can add it to your ~/.cvsrc file.
>-Larry Jones

I would add that if you have defined a module that organizes
your working directory structure differently than in your
repository, then update -d won't work either.  If a directory is
added to the module definition later, update -d won't always
find it.

update only knows about directory and file names, not module names.

however, you can always say "cvs co <module>" to get new directories.
A checkout will update existing files in your working dir the second time,
and will add any new directories.

If you provide a module alias for each top-level directory
in your repository, then you can always "cvs checkout" to
create OR update your top-level directories, and get consistent
semantics that intermix cleanly with more esoteric module definitions.

This seems easier to me.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]