[cvsnt] Best practice: .cvsignore files

[Andreas Tscharner]

Hello World,

In the company I work for, we have had a discussion among the developers
whether or not a per directory .cvsignore file should be added and
commited to module or not.

The advantages of commiting the files are clear: Not everyone needs to
have his/her own set of .cvsignore files to maintain and keep up to date

Disadvantages: If a developer has his own files in the directories, and
adds them to the ignore file, the .cvsignore file itself shows up as
modified every time an update is made (which is as annoying as
non-ignored file showing up).

What do you guys do? Do you commit the .cvsignore files or not?


Possible solution:
I thought about a possible solution and had the idea of a second ignore
file per directory, called .cvsignore.local (maybe someone has a better
name for this). What do you think about this idea?
Tony: I've posted a patch for this on support.cvsnt-dev; it's a very
simple three-liner (I hope I've got it right)

Best regards
	Andreas
-- 
Andreas Tscharner                                   starfire at dplanet.ch
-----------------------------------------------------------------------
Except for 75% of the women, everyone in the whole world wants to have
sex.                                                  -- Ellyn Mustard