[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 'cvs add' client/server semantics (was Re: Triggers)

From: Greg A. Woods
Subject: Re: 'cvs add' client/server semantics (was Re: Triggers)
Date: Wed, 2 Feb 2005 15:53:21 -0500 (EST)

[ On Wednesday, February 2, 2005 at 03:35:48 (-0800), Paul Sander wrote: ]
> Subject: Re: 'cvs add' client/server semantics (was Re: Triggers)
> Committing empty files may not be permitted by project policy.

Straw man!

(and a B.S. policy if I've ever seen one!)

> No, I don't really want total control over all client operations.  But 
> I would like more opportunities for the server to say "no".

"cvs add" (and "cvs rm") operations DO NOT EVER CONCERN THE SERVER.  Period.

They are simply the required alternatives to using an editor to change
an existing file in the working directory.  CVS is not psychic -- you
have to tell it what you mean.

> That's an exaggeration.  I really don't want to control every 
> keystroke.  I just want to keep them on the path they've agreed to 
> take, because it's easier to stay there than to wander off and find the 
> way back.

Same difference.

                                                Greg A. Woods

H:+1 416 218-0098  W:+1 416 489-5852 x122  VE3TCP  RoboHack <address@hidden>
Planix, Inc. <address@hidden>          Secrets of the Weird <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]