[Top][All Lists]

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

Re: Newbie CVS commitinfo question

From: Greg A. address@hidden (Greg A. Woods; Planix, Inc.)
Subject: Re: Newbie CVS commitinfo question
Date: Sat, 13 Jul 2002 11:24:45 -0400 (EDT)

[ On Friday, July 12, 2002 at 16:54:15 (-0700), Bryan Bunch wrote: ]
> Subject: Newbie CVS commitinfo question
>      I have a quick question about using the commitinfo admin file to 
> perform a source-file check before commiting. Mabey the tool I should be 
> using is Ageis (I've seen that project a lot in the archives), but what I 
> want to do is have a script called at the beginning of the commit process 
> which takes the following action:

No, you really do want to be using Aegis.

Trying to do what you want to do with CVS is only going to end up being
a bad hack.

>      So my initial thought is "why shouldn't the same user that has a global 
> lock on the whole repository also be able to execute read-only operations 
> like update or checkout that don't modify the repository's state?" My guess 
> is that it's simply easier to do lock management if locks aren't 
> "same-user-re-entrant" and no other cvs operations are allowed once the 
> commit starts.

What does user identity have to do with repository integrity?  The
repoisitory is not likely in a consistent state when it's locked.  It
doesn't matter who locked it or who's trying to access it.

                                                                Greg A. Woods

+1 416 218-0098;            <address@hidden>;           <address@hidden>
Planix, Inc. <address@hidden>; VE3TCP; Secrets of the Weird <address@hidden>

reply via email to

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