[EMAIL PROTECTED] on 03/06/2000 05:59:45 PM
>[ On Monday, March 6, 2000 at 15:17:02 (-0500), Noel L Yap wrote: ]
>> Subject: Re: removing the need for "cvs add file" to contact the server....
>>
>> Although "cvs watch dir" won't actually watch "dir", it does do
>> something with (ie operate on) the directory (namely, keep track of it for
>> future use). There is absolutely no way "cvs watch dir" can work on future
>> elements of "dir" if it didn't do this, no matter what the implementation of
it
>> is.
>
>You're so confused over the concepts vs. what the implementation does in
>order to make things happen that you're blind to the fact that "cvs
>watch" cannot operate on directories, no matter how much you might want
>it to! There is no ,v file for a directory -- there are only ,v files
>for (surprise) *files*! CVS is a time machine -- it remembers state in
>many ways. The trick with "cvs watch dir" being only one extremely
>minor side-show miracle it performs.
No, Greg, you're confusing the term "operate on" with "version". Just 'cos CVS
*operates on* directories doesn't mean it *versions* them. The is very true of
"cvs watch". "cvs watch" *operates on* directories though it doesn't *version*
them.
Now that (I hope) we have definitions all straightened out, it should be clear
that "cvs watch" must operate on directories in order for CVS to watch future
files. Again, this is very similar to setgid on directories -- new files don't
have setgid set on them, but new subdirectories do.
Noel
