I work on a maintenance project. There will be more than one task delivered at one time. The onsite guy will checkout the files by task, and test. If a task is OK then the working copy is tagged by task number. If any of the task is not working and it is a new file that has to be deleted in order to not tag this with other tasks. That task may be left untouched for several days till it is fixed and new tasks may be delivered in between. So it is difficult to document and exclude these files over a period of time. It will be nice if I could give a script to delete the files.
On Wed, 30 Mar 2005 10:12:29 -0500, Jim.Hyslop <[EMAIL PROTECTED]> wrote: > Antony Paul wrote: > > It will become complicated to keep the list of files. Better I will > > write a script to delete the file from CVS/Entries file. > > If this is something you are going to do on a regular basis, then sooner or > later this will turn around and bite you - hard. > > I *strongly* recommend you find another way to do this. Manually editing CVS > administrative files should be considered a one-time, last resort option to > fix one specific problem. > > -- > Jim Hyslop > Senior Software Designer > Leitch Technology International Inc. ( http://www.leitch.com ) > Columnist, C/C++ Users Journal ( http://www.cuj.com/experts ) > -- rgds Antony Paul http://www.geocities.com/antonypaul24/ _______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs