[cvsnt] Marking files as changed en masse.

[John Peacock]

Zazueta, Robert wrote:
> 'Cause sometimes I'm working on mutliple projects at once and some are
> half-done, others are fully done and not all of them should be committed at
> once for fear of breaking the build. In an ideal world, I'd only work on one
> thing at a time and have everything done and tested on my local machine at
> once before committing. But we all know what real development is like. ;-)
> 

That is what branches are for; tag what you are working on now as a branch, then 
only commit that branch (and then merge it with the HEAD branch when done).  You 
can have lots of chainsaws in the air (active branches), but you only need to 
worry about the one you are currently juggling...

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747