info-cvs archive search

21. RE: How to lock CVS for check-in (score: 172)

Author: HIDDEN

Date: Mon, 15 Oct 2001 17:53:25 -0700

In local mode, the commands in commitinfo have direct access to your "sandbox." In client/server mode, copies of the files being committed are put in a "sandbox" in /tmp on the server. A commitinfo

/archive/html/info-cvs/2001-10/msg00678.html (6,380 bytes)

22. RE: How to lock CVS for check-in (score: 170)

Author: HIDDEN

Date: Thu, 11 Oct 2001 11:07:58 -0700

Greg, 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

/archive/html/info-cvs/2001-10/msg00445.html (8,145 bytes)

23. Re: How to lock CVS for check-in (score: 165)

Author: HIDDEN

Date: 11 Oct 2001 14:41:17 -0400

GAW> [ On Thursday, October 11, 2001 at 08:24:11 (+0530), Shubhabrata GAW> Sengupta wrote: ] GAW> I'm not sure the CVS/Entries file is always available, and in any GAW> case accessing it directly is

/archive/html/info-cvs/2001-10/msg00446.html (7,739 bytes)

24. Re: How to lock CVS for check-in (score: 165)

Author: HIDDEN

Date: Thu, 11 Oct 2001 12:57:35 -0400 (EDT)

[ On Thursday, October 11, 2001 at 11:11:21 (+0530), Shubhabrata Sengupta wrote: ] Then is it not better to improve the commitinfo interface so that access to the raw CVS/Entries file is not necessar

/archive/html/info-cvs/2001-10/msg00434.html (7,736 bytes)

25. RE: How to lock CVS for check-in (score: 163)

Author: HIDDEN

Date: Thu, 11 Oct 2001 21:19:38 -0700

cvs -n stat filename works very well to get this kind of info from a commitinfo script. You get it from the CVS/Entries file through a cvs command. Jerry

/archive/html/info-cvs/2001-10/msg00501.html (6,392 bytes)

26. Re: How to lock CVS for check-in (score: 162)

Author: HIDDEN

Date: Thu, 11 Oct 2001 01:10:45 -0400 (EDT)

[ On Thursday, October 11, 2001 at 08:24:11 (+0530), Shubhabrata Sengupta wrote: ] I'm not sure the CVS/Entries file is always available, and in any case accessing it directly is a very very very bad

/archive/html/info-cvs/2001-10/msg00410.html (7,099 bytes)

27. Re: permissions on branch (score: 153)

Author: HIDDEN

Date: Tue, 15 May 2001 19:44:53 +0530

Well I have to stay back at office a little bit longer, so I though of sending the script now. I have attached a korn shell script with this mail. Here's what you should do with it. a) Check out the

/archive/html/info-cvs/2001-05/msg00487.html (11,334 bytes)

28. Re: Locking a branch (score: 135)

Author: HIDDEN

Date: Mon, 26 Aug 2002 14:30:11 -0700

Everybody makes mistakes. Good tools warn people when they're about to do something bad. This goes without saying. I think you misunderstand the goal here. Normally when a development branch reaches

/archive/html/info-cvs/2002-08/msg00261.html (8,923 bytes)

29. Re: Locking the branch (score: 133)

Author: HIDDEN

Date: Sat, 16 Apr 2005 21:26:43 -0700

Like Jim said, you can use a tag to identify the files for a release instead of locking the branch. But if you still must be able to lock the branch, for whatever reason, you can implement a pre-comm

/archive/html/info-cvs/2005-04/msg00224.html (5,815 bytes)

30. Re: Locking a branch (score: 132)

Author: HIDDEN

Date: Tue, 27 Aug 2002 07:43:07 -0400

Actually you can. The taginfo script in CVSROOT lists scripts that are run to check a tag before its committed. These scripts can prevent the tag from being applied (by returning a non-zero value). F

/archive/html/info-cvs/2002-08/msg00268.html (8,387 bytes)

31. Re: Locking a branch (score: 132)

Author: HIDDEN

Date: Mon, 26 Aug 2002 14:44:24 -0700 (PDT)

How about: ``Please don't commit to this branch until told otherwise, or you will be fired on grounds of inability to follow instructions.'' Why work with people that require a piece of software to s

/archive/html/info-cvs/2002-08/msg00260.html (6,984 bytes)

32. Re: permissions on branch (score: 127)

Author: HIDDEN

Date: Wed, 16 May 2001 08:15:19 +0530

There's a hole in that script though - in its current state it doesn't know how to lock the trunk. I haven't had time to fix that - maybe you can. I think you should include the config file in the ch

/archive/html/info-cvs/2001-05/msg00524.html (9,643 bytes)

33. Re: cvs verifying log message format per branch (score: 119)

Author: HIDDEN

Date: Tue, 24 May 2005 09:03:11 -0700

The verifymsg script for your module is run once per directory after the commitinfo script is run. For client/server operations, it is run from the server-side directory that contains a copy of your

/archive/html/info-cvs/2005-05/msg00196.html (7,404 bytes)

34. Re: Branch Locking (score: 119)

Author: HIDDEN

Date: Fri, 24 Aug 2001 09:40:14 -0700

A potential fix or way to workaround branch locking not being in CVS is to create a script in commitinfo to check whether the file is going in on a specific branch. I have not implemented this nor ha

/archive/html/info-cvs/2001-08/msg01024.html (6,341 bytes)

35. Re: branch access control (score: 113)

Author: HIDDEN

Date: Wed, 4 Sep 2002 04:30:51 -0500

It was my first thought to use cvs status, but this causes a file locking problem: cvs status: [11:04:23] waiting for markh's lock in /tag/dcacvs/CVSROOT I had presumed this was because the temporary

/archive/html/info-cvs/2002-09/msg00031.html (6,791 bytes)

36. Locking a branch (score: 110)

Author: HIDDEN

Date: Mon, 26 Aug 2002 14:12:04 -0700 (PDT)

What is the best way to lock a branch? Should I use the admin -l option? I tried this and couldn't get it to work. I have also seen some previous post suggesting to create a #commitinfo file. We woul

/archive/html/info-cvs/2002-08/msg00259.html (5,285 bytes)

37. Re: killing a branch (score: 109)

Author: HIDDEN

Date: Thu, 4 Oct 2001 12:27:15 +0530

Write a commitinfo script to lock the branch. Thanks Shubho

/archive/html/info-cvs/2001-10/msg00162.html (4,917 bytes)

38. RE: preventing commits on branches (score: 107)

Author: HIDDEN

Date: Fri, 2 May 2003 09:28:43 -0700

Hi Jason, I had a similar need, and with the help of a generous person on this list, was able to develop just such a beast. It isn't written in perl (shell script), and it is somewhat rudimentary, b

/archive/html/info-cvs/2003-05/msg00020.html (12,838 bytes)

39. Re: How can I administratively "freeze" a branch? (score: 106)

Author: HIDDEN

Date: Thu, 07 Jul 2005 09:38:03 -0500

I believe cvs_acl used as a commitinfo script, would give you the ability to lock a branch. on a fedora core system `locate cvs_acl` shows a copy to be in /usr/share/cvs/contrib/cvs_acls or you could

/archive/html/info-cvs/2005-07/msg00073.html (6,963 bytes)

40. Re: "Locking" branches (score: 104)

Author: HIDDEN

Date: Fri, 05 Jan 2001 11:37:24 -0500

we handled this by forcing versions on the branches when we create them with the "cvs ci -F" command then we wrote a reserve script that gets the revision from the CVS/Entries file and locks it "admi

/archive/html/info-cvs/2001-01/msg00068.html (27,462 bytes)