Re: removing the need for "cvs add file" to contact the server....

[Greg A. Woods]

[ On Thursday, March 2, 2000 at 11:37:10 (-0500), Noel L Yap wrote: ]
> Subject: Re: removing the need for "cvs add file" to contact the server....
>
> >  You are failing to
> >understand the temporal nature of CVS (its most central reason for
> >being!).  This command does in fact operate on the files in a directory,
> >and indeed not just on those that exist today, but those that might
> >exist at any time in the future while the "watch" is still in effect.
> 
> In order for it to work on future files and directories, it must operate on
> directories.  It's like the setgid bit on directories.

You mean you can read my explantion above and still spout that
nonsense?!?!?!?  You really have a *LOT* to learn about CVS....

You're not seeing the forest for the trees man!

> I have no argument with this in general.  My argument is that only "cvs co",
> "cvs export", and "cvs up" should deal with this issue.  You seem to think that
> all CVS commands (at least "cvs add") should at least do a half-hearted job of
> trying to prevent working on empty hierarchies.

In case you've missed the connection, again:  "cvs add", at least so far
as my proposal is concerned, is a direct sibling, almost a twin, of "cvs
import".

-- 
                                                        Greg A. Woods

+1 416 218-0098      VE3TCP      <[EMAIL PROTECTED]>      <robohack!woods>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>