Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Yes, you would create a new folder in the folder you happened to be in when you issued the command. This new folder would be named 'mymodule' and would contain *everything* from the repository module including all subfolders. If you want to check out a specific file it is very simple: cvs co mymodule/sourcefiletocheckout modules file ------------- Normally not used! Only in special cases do you need to mess with the modules file. For example if you have a source project which contains some common stuff in a subfolder and now you want to create a new project in which you want to use the common stuff from the old project. In this case you create a new folder with the new project files *except* the common stuff, then you add or import it to your repository thus creating a cvs module, say named newproj1. Then you check out CVSROOT to get at the modules file, you edit it by adding a new definition of a module newproj where you specify the two modules newproj1 and oldproj/common as follows: common oldproj/common newproj &newproj1 &common Commit the changes to CVSROOT. If you now check out 'newproj' then you will find that the sandbox contains a folder 'newproj' with two folders named 'newproj1' and 'common' respectively (with all the files of course). And CVS *is* smart enough to detect *and merge* the changes you have locally with whatever you get from the repository. :-) /Bo On Tue, 26 Mar 2002 20:55:23 +0000 (UTC), "Unknown Dude" <nobody at nowhere.com> wrote: >So that would grab the entire source tree of the mymodule module, correct? > >Can you specify an individual file? >cvs co mymodule sourcefiletocheckout > >Once I add the module to the modules file how would I add it to the >repository? >cvs add mymodule mysourcefile > >Also, if I have modified 1 of the files and I do a co on the entire module >will it overwrite my changes or is it smart enough to detect that? > >Thanks again, >Sorry for all the questions but Im trying to get all this set up in a single >day. > > > >"Bo Berglund" <bo.berglund at telia.com> wrote in message >news:3ca0dcaa.1285156390 at news.cvsnt.org... >> On Tue, 26 Mar 2002 19:46:31 +0000 (UTC), "Unknown Dude" >> <nobody at nowhere.com> wrote: >> >> >If I have a repository called /TEST and I want to access a module called >> >mymodule, how do I set up my cvsroot on the client side >> > >> >cvsroot=:pserver:joe at cool.com:/TEST/mymodule? >> >cvsroot=:pserver:joe at cool.com:/TEST? and then refer to the module during >> >checkouts? >> > >> >Please advise >> > >> >> This should do it: >> set cvsroot = :pserver:joe at cool.com:/TEST >> cvs login (enter password) >> cvs co mymodule >> >> >> >> /Bo >> (Bo Berglund, developer in Sweden) >> _______________________________________________ >> Cvsnt mailing list >> Cvsnt at cvsnt.org >> http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs > > >_______________________________________________ >Cvsnt mailing list >Cvsnt at cvsnt.org >http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs /Bo (Bo Berglund, developer in Sweden) _______________________________________________ Cvsnt mailing list Cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs