[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

cvs add behavior

From: Edward Dunkle
Subject: cvs add behavior
Date: Wed, 27 Feb 2002 14:09:37 -0600

I suppose this is technically an enhancement request, but it sure seems like
a major oversight at least.

There doesn't seem to be an obvious way of blocking certain files from being
added to the repository.  For instance, let's say you have adopted a policy
of NOT keeping *.class files in CVS.  The cvsignore file allows you to
configure this behavior for the 'update' (and some other) commands, but
'add' is unaffected.  This allows anyone to inadvertantly 'add' a file that
is undesirable.  Perhaps no one would actually add a .class file explicitly
but perhaps they have added a handful of files in a new directory, compiled
them, and then issue 'cvs add *.*', or perhaps there is a specific filename
you want to disallow, like build.properties and not everyone is aware that
it should not be added.  

It seems natural to assume that one could NOT add a file that was purposely
listed in the cvsignore file.  This should be the default behavior of the
'add' command - to act just like the 'update' command in regards to ignored
files.  If, for some reason, a particular file is needed that is usually
ignored, you could support a command option (like -f) to FORCE the add
regardless of the default ignore behavior.

I am aware that one could write a program or script for commitinfo to run,
but this extra effort for each repository is undesirable.  

Thank you for considering this request.  I would be greatly interested in
understanding what objections there could be to this proposal.

Ed Dunkle

reply via email to

[Prev in Thread] Current Thread [Next in Thread]