[EMAIL PROTECTED] on 02/29/2000 01:08:54 PM
>[ On Tuesday, February 29, 2000 at 09:00:01 (-0500), Noel L Yap wrote: ]
>> Subject: Re: removing the need for "cvs add file" to contact the server....
>>
>> In order for "cvs add empty-hier; cvs ci" to work properly, "cvs ci" will
have
>> to be changed to create repo directories whenever it spots a local CVS admin
>> directory existing within a local directory not existing within the repo.
This
>> would be a simple behavioural change from creating repo directories only when
it
>> spots newly added files within the local directory.
>
>Nope. That's completely wrong. My proposal already shows how "cvs ci"
>will work and it's not like you suggest at all -- almost the opposite in
>fact.
Fine, I'll work on fixing your changes once you post them.
>You seem to have some fictional and very skewed concepts about what CVS
>does and what it is supposed to do.
This is balanced by your limited view of what it does and what it can do.
> CVS only manages files and not
>directories.
This has already been argued. CVS does manage directories but doesn't version
them. I don't know what your definition of manage is, but to me it's partially
the ability to create. CVS is able to create directories (although we disagree
under what conditions they should be created). Furthermore, CVS does handle
directories in a special way (eg "cvs watch dir") regardless of what you think
should be.
> Assuming an up-to-date workspace then "cvs add empty-hier;
>cvs ci" must do nothing (just as the final "cvs ci" does nothing today)!
The "cvs add empty-hier" must create CVS admin subdirectories. The following
"cvs ci" should create the directories within the repo (just as the current "cvs
ci" should do today).
>Until you understand and accept this fact you'll be unable to go
>forward.
I understand the current situation and your proposal. I don't accept either.
> Your arguments all seem to rest on this being false and thus
>they must all crumble to nothing without it.
*Your* arguments are unfounded. CVS does manage (however limited) directories.
Having CVS admin directories within empty hierarchies cannot be prevented (not
that you ever said they could, but your "optimisation" seems to imply the
notion). Having CVS be able to create empty directories within the repo isn't
dangerous.
So, go ahead with the implementation of your proposal. I'll fix it once you
post it.
Noel
