I don't mind either way. I have found it generally useful to have them provided, and have wished the plib would do the same (for .deps directories, in particular).
However, I have only ever worked on small patches, never adding files, so I have never needed to take note of the "?" and "unknown file" messages that CVS prints. Even with the .cvsignore files, I still get a whole bunch of these messages, many of which are from local back-up files etc., but some of which I think should be added to the checked-in .cvsignore files (I can't check at the moment). I now always filter out lines starting with a question mark from the output of cvs update and cvs diff. If I was adding files I probably would want correct and complete .cvsignore lists. (I could add one in my home directory to describe most of my local back-up files.) While these files are in CVS people must occasionally update them. Not a very big deal, but in general the fewer files the better. About 22 of the 32 Flight Gear .cvsignore files contain just "Makefile", "Makefile.in" and ".deps". These could perhaps be replaced with a per-repository list in `$CVSROOT/CVSROOT/cvsignore'. - Julian David Megginson wrote: > A while ago, I added .cvsignore files to the FlightGear, SimGear, and > TerraGear CVS repositories to let CVS know to ignore generated files > like executables and scripts, and cut down on the noise in CVS > sessions. I now think that was a mistake, since people probably want > their own, local, customized .cvsignore files if they want any at > all. Would anyone object to my removing them from the repositories? > Does anyone else care? _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
