[Top][All Lists]

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

RE: How to lock CVS for check-in

From: Pyatt, Scott
Subject: RE: How to lock CVS for check-in
Date: Thu, 11 Oct 2001 11:07:58 -0700


Are you arguing that this functionality be added as part of standard CVS in
a future release (which I would prefer) or are you simply suggesting to
Shubhabrata to change the CVS code for his or her own needs?


-----Original Message-----
From: address@hidden [mailto:address@hidden
Sent: Thursday, October 11, 2001 9:58 AM
To: CVS-II Discussion Mailing List
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 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
> 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]