[EMAIL PROTECTED] on 03/13/2000 11:47:53 PM
>> >Although I would lean towards honouring the "add" request, it might be
>> >prudent to at least print a warning message indicating that the
>> >directory would normally have been ignored if it had been traversed from
>> >the "root" of the module instead of from within itself....
>>
>> I was leaning towards the opposite, namely honouring the .cvsignore. It
>> shouldn't be too difficult either. As CVS is looking for the ancestor CVS
admin
>> subdirectory, it should check to see if any ancestor directories is listed in
>> any of the .cvsignore files it finds. If any do, the "cvs add" should be
>> abandoned.
>
>However the implication of actually being within the "previously thought
>to be ignored" directory when calling upon CVS is that one actually does
>really want to add the files in "this" directory. As I say I can see
>why a warning might be handy, but given the relatively innocuous effect
>I don't see why it should be disallowed.
I disagree, the normal context of "cvs command" is to ignore ignored files. If
one didn't want it ignored (specially in an add command), one would specify the
file (ie "cvs add file"). So, "cvs add" within an unknown directory should
honour the ancestor .cvsignore files. If one really did want the stuff added,
it's still possible (ie CVS doesn't outright disallow it).
Noel
