[EMAIL PROTECTED] on 02/17/2000 11:12:14 PM
>[ On Thursday, February 17, 2000 at 17:42:28 (-0500), Noel L Yap wrote: ]
>> Subject: Re: removing the need for "cvs add file" to contact the server....
>>
>> This is fine by me. Again, note that the above doesn't mention "cvs add
>> empty-hier" at all.
>
>I'm not sure what you're getting at by that. Yes, "cvs add emtpy-dir"
>will not fail. However it won't do *anything* either. It's exactly
>equivalent to "cvs add dir-with-only-ignored-files".
>
>> >> They also shouldn't be ignored by "cvs add".
>> >
>> >They won't be purely ignored -- but nothing can happen unless there are
>> >un-ignored files within to be operated on.
>>
>> One more time: it should be "cvs co", "cvs export", and "cvs up" that handle
>> this, not "cvs add" or "cvs ci".
>
>Now I'm sure I don't know what you're getting at....
>
>"cvs add" only adds un-ignored or explicitly specified files. "cvs ci"
>only commits ``changes''.
What I'm getting at is that "cvs add dir" should create CVS admin subdirectories
whether or not the hierarchy is empty. "cvs add dir" shouldn't differentiate
between empty (including those that contain only ignored files) and non-empty
hierarchies. You still haven't shown how it can be dangerous to do so. After
all, this is only occurring within the local directories right?
I also contend that "cvs ci" will create those newly added directories into the
repository whether or not they are empty hierarchies. Again, you haven't shown
how this is dangerous. OTOH, I've shown an example where this could be used
wisely by a site's processes (ie so that the newly added directories are owned
by the cvs admin).
Noel
