Re: import vs cvs co -c
E B wrote: > > how do I create a module from the client? > If I do it with cvs import, I dont see it > using cvs co -c. You need to add it to the $CVSROOT/modules file. -Matt ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: import vs cvs co -c
cvs man page: Use the -c option to copy the module file, sorted, to the standard output, instead of creating or modifying any files or directories in your working directory. It merely shows a sorted modules file. IMHO, CVS Admin needs to include your project in a modules file Visit iWon.com - the Internet's largest guaranteed cash giveaway! ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: import vs cvs co -c
You have to edit the modules file in $CVSROOT/CVSROOT. > -Original Message- > From: E B [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 07, 2002 1:34 AM > To: [EMAIL PROTECTED] > Subject: import vs cvs co -c > > > how do I create a module from the client? > If I do it with cvs import, I dont see it > using cvs co -c. > > > > __ > Do You Yahoo!? > Everything you'll ever need on one web page > from News and Sport to Email and Music Charts > http://uk.my.yahoo.com > > ___ > Info-cvs mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/info-cvs > ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: import vs cvs co -c
Probably you guys havent read my mail clearly. How does a client have access to the modules files on the server? Is there any cvs admin command that will do this? --- "Walsh, Matthew" <[EMAIL PROTECTED]> wrote: > You have to edit the modules file in > $CVSROOT/CVSROOT. > > > > > -Original Message- > > From: E B [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, February 07, 2002 1:34 AM > > To: [EMAIL PROTECTED] > > Subject: import vs cvs co -c > > > > > > how do I create a module from the client? > > If I do it with cvs import, I dont see it > > using cvs co -c. > > > > > > > > __ > > Do You Yahoo!? > > Everything you'll ever need on one web page > > from News and Sport to Email and Music Charts > > http://uk.my.yahoo.com > > > > ___ > > Info-cvs mailing list > > [EMAIL PROTECTED] > > http://mail.gnu.org/mailman/listinfo/info-cvs > > __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: import vs cvs co -c
you need to explictly checkout the CVSROOT directory either locally on the server or on a client system by doing: cvs co /yourpathtorepository/CVSROOT cd /yourpathtorepository/CVSROOT vi modules add your new modules with the correct syntax cvs ci modules Now the module will recognized by CVS on your server and you can do operations using it... cheers, -teala -Original Message- From: E B [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 07, 2002 9:24 PM To: Walsh, Matthew; [EMAIL PROTECTED] Subject: RE: import vs cvs co -c Probably you guys havent read my mail clearly. How does a client have access to the modules files on the server? Is there any cvs admin command that will do this? --- "Walsh, Matthew" <[EMAIL PROTECTED]> wrote: > You have to edit the modules file in > $CVSROOT/CVSROOT. > > > > > -Original Message- > > From: E B [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, February 07, 2002 1:34 AM > > To: [EMAIL PROTECTED] > > Subject: import vs cvs co -c > > > > > > how do I create a module from the client? > > If I do it with cvs import, I dont see it > > using cvs co -c. > > > > > > > > __ > > Do You Yahoo!? > > Everything you'll ever need on one web page > > from News and Sport to Email and Music Charts > > http://uk.my.yahoo.com > > > > ___ > > Info-cvs mailing list > > [EMAIL PROTECTED] > > http://mail.gnu.org/mailman/listinfo/info-cvs > > __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: import vs cvs co -c
> cvs co /yourpathtorepository/CVSROOT > cd /yourpathtorepository/CVSROOT > vi modules > add your new modules with the correct syntax > cvs ci modules Is this right? I think it should be cvs co CVSROOT cd CVSROOT vi modules cvs ci modules -- Fred Brehm, Sarnoff Corporation, [EMAIL PROTECTED] http://www.sarnoff.com/digital_video_informatics/vision_technology/index.asp ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: import vs cvs co -c
On Thursday, February 7, 2002, at 11:24 PM, E B wrote: > Probably you guys havent read my mail clearly. > How does a client have access to the modules files > on the server? Is there any cvs admin command that > will do this? > You checkout CVSROOT/modules, make your changes and then commit it. However, if you're just a user of the repository, you my not have permission to make changes to the administrative files. Wade ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: import vs cvs co -c
Teala Spitzbarth writes: > > you need to explictly checkout the CVSROOT directory either locally on > the server or on a client system by doing: > > cvs co /yourpathtorepository/CVSROOT > cd /yourpathtorepository/CVSROOT > vi modules > add your new modules with the correct syntax > cvs ci modules Right idea, wrong details: cvs co CVSROOT/modules # or you can check out the entire CVSROOT directory cd CVSROOT # edit modules cvs ci -Larry Jones I think if Santa is going to judge my behavior over the last year, I ought to be entitled to legal representation. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
