[EMAIL PROTECTED] on 03/03/2000 12:10:11 AM
>[ 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....
Please help me out here. I'm trying to figure out where our disconnect is.
I'm saying that "cvs watch" does indeed work on directories in order to work on
future files/sub-directories. The way it does this is by storing some
information within CVS/fileattr. This mechanism is similar to how group
ownerships are controlled by setgid on directories.
Now, you're saying that "cvs watch" does not work on directories and that it
only works on current and future files. What do you think it does in order for
it to work on future files?
>> 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".
The major difference between "cvs add" and "cvs import" is that "cvs add" should
not affect the repo directly while "cvs import" does (in fact, it is possible to
create empty modules (and therefore empty directories) with "cvs import").
Upon reading your proposal again, I caught that you intend "cvs co
non-existent-module" to create an empty working directory iff
non-existent-module is described within CVSROOT/modules. This sounds like:
1. You're trying to replace "cvs import" with "cvs co CVSROOT; add new-module to
CVSROOT/modules; cvs ci CVSROOT; cvs co new-module; create stuff in new-module;
cvs ci new-module". I'm not sure how I feel about this yet, but it should
definitely be discussed further.
2. CVSROOT/modules will have a more important role. I like this idea but I'm
not sure if your proposal is the way to go about doing it.
Noel
