Russ Allbery wrote:
>
> Ken Chou <[EMAIL PROTECTED]> writes:
>
> > I have a question regarding the 'add' command in cvs. The repository in
> > our group is somehow exhibiting the following behavior: when someone
> > creates a new directory in his local version, then does a 'cvs add', it
> > appears that no one else in the group gets the new directory when doing
> > an 'update' subsequent to this action. The file permissions in the
> > repository appear fine and the cvs directory and log files appear fine
> > in the new, local directory of the person who created it.
>
> Are there any files in the new directory? If not, are all of your users
> using the -P flag to update? That would explain it.
>
> --
> Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
I think what you want is cvs update -d to get the new directory. Here's
the notes from the manpage's update section:
Use the -d option to create any directories that
exist in the repository if they're missing from the
working directory. (Normally, update acts only on
directories and files that were already enrolled in
your working directory.) This is useful for updating
directories that were created in the repository since
the initial checkout; but it has an unfortunate side
effect. If you deliberately avoided certain directo-
ries in the repository when you created your working
directory (either through use of a module name or by
listing explicitly the files and directories you
wanted on the command line), then updating with -d
will create those directories, which may not be what
you want.
--
Cheers,
Derek
_____________________________________________________________________
Derek Scherger Echologic Software Corporation
mailto:[EMAIL PROTECTED] http://www.echologic.com
