Thank you! That's what I needed to know. I had to place the .cvsignore file into the test directory. Interestingly enough, cvs update then started flagging that file. So I add/commit'ed it as well. Much nicer, at the others on the project will get this improvement as soon as they update. Cool. -- Allen Brown work: Agilent Technologies non-work: http://www.peak.org/~abrown/ [EMAIL PROTECTED] [EMAIL PROTECTED] Isn't it a bit unnerving that doctors call what they do "practice"? --- George Carlin
On Sun, 19 Dec 2004, Jacob Meuser wrote: > On Sun, Dec 19, 2004 at 12:39:14PM -0800, Allen Brown wrote: > > All: > > > > I am working with a project in CVS. There are about 20 files managed > > there. In addition, another 20 or so files are created as part of the > > testing of the project. > > > > Whenever I run 'cvs update' it bitches about these files not being > > managed. I want to tell CVS to just ignore them. > > use .cvsignore files. > > > On the man page for cvs it talks about suppressing the update > > complaints using a pattern in ~/.cvsrc. It says the pattern is the > > same as the one for cvswrappers, which then refers to "see node > > `Wrappers' in the CVS manual". > > > > I don't know what manual they are referring to, but it isn't > > the man page. Does anyone here know what the correct format is for > > this? It would be nice to suppress the complaints about the > > following files: > > > > test/cn_*.test > > test/cn_*.diff > > test/cn_*.out > > $ cat test/.cvsignore > cn_*.test > cn_*.diff > cn_*.out > > > I've tried a number of patterns to no avail. > > I don't think you can go into subdirectories. > > -- > <[EMAIL PROTECTED]> > > > _______________________________________________ > EUGLUG mailing list > [EMAIL PROTECTED] > http://www.euglug.org/mailman/listinfo/euglug > _______________________________________________ EUGLUG mailing list [EMAIL PROTECTED] http://www.euglug.org/mailman/listinfo/euglug
