[Top][All Lists]

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

Re: How to lock CVS for check-in

From: Shubhabrata Sengupta
Subject: Re: How to lock CVS for check-in
Date: Thu, 11 Oct 2001 11:11:21 +0530

At least in pserver access it is and I think it is also available in for
local repository access as well. I am not sure about :ext: access though.

I agree that its contents and its structure is entirely internal to CVS and
may change without notice from one CVS release to another. I do not write
anything into CVS/Entries at all - I use it to read the branch name of the
file that is being committed. So that way there is very little danger of
corrupting that file. Of course I make assumptions about the structure of
the file and that may change from one CVS release to another - I am ready to
change the regex I use to grep the branch name when that happens. The
advantages I get from controlling access to branches through commitinfo
script outweighs the risk in my case.



-----Original Message-----
From: Greg A. Woods <address@hidden>
To: CVS-II Discussion Mailing List <address@hidden>
Date: Thursday, October 11, 2001 10:47 AM
Subject: Re: How to lock CVS for check-in

>[ On Thursday, October 11, 2001 at 08:24:11 (+0530), Shubhabrata 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
>> is always available to the commitinfo script.
>I'm not sure the CVS/Entries file is always available, and in any case
>accessing it directly is a very very very bad hack.  Its contents should
>be private and for CVS internal use only.  The fact that some of its
>structure is documented in the manual is not permission to go mucking
>about in it unless you're cleaning up some form of corruption or another.
> Greg A. Woods
>+1 416 218-0098      VE3TCP      <address@hidden>     <address@hidden>
>Planix, Inc. <address@hidden>;   Secrets of the Weird <address@hidden>
>Info-cvs mailing list

reply via email to

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