[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: Fri, 12 Oct 2001 09:24:00 +0530

Absolutely - I would be relieved if commitinfo scripts get the branch
information as well. But I am reluctant to go do it myself because of my
unfamiliarity with CVS code and lack of time to gain some familiarity with
it. Though there have been patches floating around which achieved the same,
for some reason or the other they have not been integrated into the CVS
codebase. I could have built a patched CVS binary and use it, but the shop
where I work, the CVS server is controlled by the IT department (since it is
shared among a whole bunch of groups) and they are extremely reluctant to
accept such patches.



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

>[ On Thursday, October 11, 2001 at 11:11:21 (+0530), Shubhabrata Sengupta
wrote: ]
>> Subject: Re: How to lock CVS for check-in
>> 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
>> 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
>> 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
>> 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.
>Then is it not better to improve the commitinfo interface so that access
>to the raw CVS/Entries file is not necessary?
> 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]