.cvsignore

From: bill_kempf (williamkempf_at_[hidden])
Date: 2002-02-25 15:21:18

I'd like to start using .cvsignore files at least in the 
Boost.Threads directory branch.  However, Boost doesn't appear to be 
using this facility currently (the only .cvsignore file in the whole 
repository is in boost/status).  So, before using this facility I 
thought I'd ask about the appropriateness of doing so.  Beman 
suggested I ask on the list in case any other Boost users have 
experience with .cvsignore and can provide opinions on this topic.

In case anyone doesn't know about .cvsignore, here's a brief 
description of what it is and how you use it.

.cvsignore is a file placed in any directory that's under CVS control 
(it works on a per-directory basis instead of per-repository basis) 
and allows you to specify certain files (including wildcard 
specifications) as "ignored". If a file meets any of the 
specifications in the .cvsignore file in its directory then CVS won't 
attempt to update/commit/etc the file.  So in build directories that 
use the Jam system a .cvsignore file could be added with the 
following contents:

bin
*.pdb

This will cause CVS to ignore the bin directory generated by Jam and 
any .pdb files generated by VC++.  I use Dream Weaver to edit HTML 
files and it would also be nice to add _notes to the .cvsignore file 
in doc directories to ignore the _notes directory it uses for 
metadata.  I'm sure there are plenty of other things in the Boost 
repository that developers would like to be ignored by CVS commands.

The only reason for not using .cvsignore files that I can see is that 
another file(s) will be included in the CVS archive.  I don't think 
this is a compelling reason to not use .cvsignore (and use it a LOT), 
but since Boost hasn't been using them yet I thought I should ask 
before adding them to the Boost.Threads directories.

Thoughts, opinions, information?

Bill Kempf