[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: segmenting a CVS repository

From: Todd Denniston
Subject: Re: segmenting a CVS repository
Date: Fri, 28 Jan 2005 11:45:17 -0500

> 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/

For more info please look at the Manual, and try 'cvs checkout --help'

> Is
> there an alternative to breaking the project up into seperate modules,
> like a more appropriate command for the situation? 
See above

> Or have I just named
> the reason for modules?:-)
Possibly, if it makes sense for everyone on the project to only be wanting
specific sub trees (you can also use modules to group sub trees). if it is
just you, then the above methods are probably preferable.

Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter

reply via email to

[Prev in Thread] Current Thread [Next in Thread]