[cvsnt] Marking files as changed en masse.

Torsten Martinsen torsten at tiscali.dk
Wed Sep 11 16:11:09 BST 2002

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.

Maybe I'm being a bit thick here, but why don't you just do a single commit
(or tag) from the top level directory?


----- Original Message -----
From: "Zazueta, Robert" <RZazueta at academyart.edu>
To: <cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook>
Sent: Wednesday, September 11, 2002 02:17
Subject: [cvsnt] Marking files as changed en masse.

> This is sort of a general "Best practices" question. I have used CVS to
> maintain files for websites for quite some time. In these situations, you
> often have a ton of code that is all tied together (i.e. headers, footers,
> body pages, code libraries, etc.) but live in different parts of the drive
> and may all need to be changed at once. Or, as another example, you
> sometimes need to add something to several pages at once, but don't want
> commit or tag them until all the work has been done for fear of breaking
> build.
> How do you keep track of all of the files you've changed? I use WinCVS and
> I'm beginning to wish for a function that will allow me to make something
> like a "local tag" that I can attach to a series of files, then tell CVS
> commit or tag or whatever all of them in one fell swoop. Is there a way to
> do something like this now in standard CVS? Does CVSNT support that?
> Anything has to be better than writing the files down on a pad of paper
> crossing my fingers.

More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook