Chuck, I am aware of that patch you are referring to - I found it when I was searching for a way to lock branches. The problem with the setup that I have here is - I am not allowed to patch the CVS s
Shubho, Sometime ago, I posted patches by John Cavanaugh that can be used for branch locking. The patches are for version 1.11 of CVS but work for the most current version as well. One chunk of the p
The patch, by John Cavanaugh, is implemented in such a way that the feature can be enabled or disabled. In disabled state, there would be no backwards compatibility issue. The patch comes complete w
Why is there not more useful information passed to cvs at commit time? I think that the branch tag would be an fantastic addition.. This would be an extremely easy way to implement branch locks. no?
Hi Karthik, This issue has been raised multiple times in the info-cvs mailing list. You may find review of the list useful. For an example of one of the threads, follow this link: http://mail.gnu.org
Use the cvs admin -l<branch_name>. This will lock the latest revision on that branch. Hi there! Does anyone have a script to lock a CVS branch to be used with commitinfo? I started to write one, but
I suggest you'll need to write a commitinfo script that'll examine any commits and reject them if they're on one of the locked codestreams. See http://cvshome.org/docs/manual/cvs_18.html#SEC165 Andy
Yes it is - I use that same kind of scenario down here in my workplace. I had posted a script to do this sometime back on this list, a Python script I forget the name of the author - apologies) was a
Hi there! Does anyone have a script to lock a CVS branch to be used with commitinfo? I started to write one, but my boss wants one in place ASAP. Please, help. Thanks
Is CVS/Entries available to the commitinfo script when the repository is on a Unix server and the developer is working on an NT client (pserver)? If so, I can put something together. With companies l
Well, you need a list of users that are either in the set of allowed or in the set of disallowed. It is up to you how to implement it. The code was just provided as an example approach. I would sugg
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. Tha
"How to lock a branch?" This seems to be the number one question posted to info-cvs. I posted it myself two years ago. Is there anyway this enhancement can get rolled into a future release of cvs (e.
You can selectively lock branches, but only if the branch info can get passed to your commitinfo script. We have "enhanced" the commitinfo interface locally to send additional parameters we find usef
Greg, I don't know your environment, but branch locking is a common mechanism for allowing read-only access to a branch. It's really quite useful and given the high frequency that this issue pops up
You can use "cvs -n status" to get the info despite the lock. -- Pierre Asselin Westminster, Colorado --= Posted via Newsfeeds.Com, Uncensored Usenet News =-- http://www.newsfeeds.com - The #1 Newsgr
[ On Thursday, October 11, 2001 at 15:14:47 (-0700), Pyatt, Scott wrote: ] Wel, "DUH!" :-) I think the right phrase would be: "not alone in your confusion". Do you have any idea how big the three mai
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 som
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 entir
To recap, I'm looking to a way to lock branches so that people don't accidentaly check out or commit to an 'inactive' branch. I also need the solution to work for those accessing CVSROOT vi the :ext: