Paul Sander <[EMAIL PROTECTED]> writes: > On Feb 1, 2005, at 2:51 AM, [EMAIL PROTECTED] wrote: > > > Paul Sander <[EMAIL PROTECTED]> writes: > >> Would you post a message stating your point of view, completely, > >> please? Thanks! > > > > I need a way to generate 'cvs diff' against read-only repository. To > > achieve this it's enough to fix 'cvs add' so that it either doesn't > > contact the repository at all, or just doesn't require write permission > > to the repository to succeed. > > > > As a response to the question, I've got a reference to the discussion > > about new 'cvs add' implementation, where you, Paul, argue in favor of > > new implementation of 'cvs add' to contact the repository to run some > > new scripts you called add-time triggers. I then tried to tell that I'm > > yet another person here who is against such a thing and tried to suggest > > > another way of achieving your actual goal, -- checking something against > > > repository at add-to-working-copy time using existing commit-time > > triggers. > > There are two proposals on the table. The first is Greg Woods' > proposal to make "cvs add" be a purely local operation. The second is > mine, which implements add-time triggers that require calling the > server but in a way that the user can opt out of them when invoking > "cvs add". > > Does that meet your need?
I like Greg's proposal and explicitly stated it first time I touched this issue after reading relevant thread I've been pointed at. I don't like your proposal and explicitly stated it first time I touched the issue. Though your proposal is in fact orthogonal to my original concern with 'cvs diff' and thus I don't care that much about it. -- Sergei. _______________________________________________ Info-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-cvs
