[Top][All Lists]

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

Re: How to lock CVS for check-in

From: Jake Colman
Subject: Re: How to lock CVS for check-in
Date: 11 Oct 2001 14:41:17 -0400
User-agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.1 (Channel Islands)

>>>>> "GAW" == Greg A Woods <address@hidden> writes:

    GAW> [ On Thursday, October 11, 2001 at 08:24:11 (+0530), Shubhabrata
    GAW> Sengupta wrote: ]
    >> Subject: Re: How to lock CVS for check-in
    >> Wondering why this enhancement is needed in the commitinfo interface
    >> when you can always get the branch information out of the CVS/Entries
    >> file which is always available to the commitinfo script.

    GAW> I'm not sure the CVS/Entries file is always available, and in any
    GAW> case accessing it directly is a very very very bad hack.  Its
    GAW> contents should be private and for CVS internal use only.  The fact
    GAW> that some of its structure is documented in the manual is not
    GAW> permission to go mucking about in it unless you're cleaning up some
    GAW> form of corruption or another.

So what do _you_ recommend for implementing branch locking?


Jake Colman                     

Principia Partners LLC                  Phone: (201) 946-0300
Harborside Financial Center               Fax: (201) 946-0320
902 Plaza Two                          E-mail: address@hidden
Jersey City, NJ 07311        

reply via email to

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