Try it on a server with a modules file. Move at a temporary directory and try.....
.
cvs -d :psrever:[EMAIL PROTECTED]:/home2/cvsroot login
(password:guest)
cvs -d :psrever:[EMAIL PROTECTED]:/home2/cvsroot co -c
cvs -d :psrever:[EMAIL PROTECTED]:/home2/cvsroot co modules
The -d option points you at the cvs repository for cvs. The 'co -c' shows you the
output of the modules file and the 'co modules' checks out the modules file so you
can check it out.
Or you can read about it in the manual,
http://www.cvshome.org/docs/manual/cvs_18.html#SEC155
Hope it helps....
~j
--
Jason Williams
OpenAvenue, Inc.
Noel L Yap wrote:
> You need to fill in CVSROOT/modules yourself.
>
> Noel
>
> [EMAIL PROTECTED] on 2000.08.08 13:43:47
>
> To: [EMAIL PROTECTED]
> cc: (bcc: Noel L Yap)
> Subject: Re: Listing modules in cvs
>
> cvs co -c didn't do anything. It just exits without displaying anything to the
> console. The modules file does not have any entries other than #comments
> Can anyone help me out here? Did I miss a vital configuration step?
> I have module in the repostry called hpu that can be checked out using "cvs
> checkout hpu" and committed.
> CVSWEB doesn't work either, it doens't display entries other than folders in
> the repostry.
>
> > A 'cvs co -c' will give you a list of the modules contained in
> > CVSROOT/modules. This could be used to give you the desired results if
> > you list the desired imports. Read the comments in the modules file for
> > more information.
> >
> > ~j
> > --
> > Jason Williams
> > OpenAvenue, Inc.
>
> ____________________________________________________________________
> Get free email and a permanent address at http://www.netaddress.com/?N=1
>
> This communication is for informational purposes only. It is not intended as
> an offer or solicitation for the purchase or sale of any financial instrument
> or as an official confirmation of any transaction. All market prices, data
> and other information are not warranted as to completeness or accuracy and
> are subject to change without notice. Any comments or statements made herein
> do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
> subsidiaries and affiliates.
