I am taking this back to the list, often someone else there will see things with less or different blinders than me.
Tate Austin wrote: > > I'm not simply referring to checking out files, I am also referring to > cvs update. It seems that most cvs commands are designed to recurse > through all the subdirectories you are executing them from. This is True, but many of the commands which do this also have an option to do "Local directory only (not recursive)". I do not know the work environment you are in, but I am used to needing to test my changes against what is current in the rest of the repo before committing, so I have the whole baseline, work out my changes, do an update fix anything that conflicted, test, fix any logical conflicts caused by the update, commit the work. > What I'm > wondering is do I have that notion wrong, or is making lots of modules > part of the way cvs was designed? That is a choice that the each project leader/CM manager makes, it is not imposed by CVS. Lots of modules might imply that the system was made in a modular fashion or that there was little planning or control of the way/when directories were created. > When I used eclipse having a gui made > things very simplified, now on a CLI I see it is a different world. > You might be interested in http://www.wincvs.org/ which has a unix GUI. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Todd Denniston > Sent: Friday, January 28, 2005 11:45 AM > To: Tate Austin; cvs > Subject: Re: segmenting a CVS repository > > > Tate Austin wrote: > > > > I'm used to using CVS thrugh GUI's (eclipse, etc) and I'm now in an > > environment where we are command line bound and I have a sizeable > > project in a CVS repository. When I make one change to one file, it > > is simply too time consuming to do cvsupdate from the CLI to just get > a few files. > > did you mean > 'When I want to make a change to one file, it is simply too time > consuming to do cvs checkout of the whole repository to just get that > file.'? > > Some people would indicate that you really only need to do the full > checkout once and then update before starting new work so you only incur > the big wait once (Disk space is cheap today, for most coding projects). > But you can if you want check a single file out of cvs, like so: > cvs checkout module/subpath/filename > if you only want one sudirectory and none of it's sub-directories try: > cvs checkout -l module/subpath/ -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter _______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
