[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: How to lock CVS for check-in
From: |
Jerry Nairn |
Subject: |
RE: How to lock CVS for check-in |
Date: |
Mon, 15 Oct 2001 17:53:25 -0700 |
> From: David Everly [mailto:address@hidden
> Sent: Friday, October 12, 2001 5:03 PM
> cvs -n stat filename seems only to work from a 'sandbox' point of
> view. How would I use that in the context of a commitinfo script?
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 command can use
either:
cvs -n stat filename
or
cvs -n log -h filename
to find out if the file is on a branch in either case.
I use the "-n" option to cvs because at one point, trying to use these
commands while doing a commit would have you waiting for your own lock. Even
though these commands would not modify your workspace or the repository
using "-n" or not, when you used "-n" you didn't have to wait for the lock.
I'm not sure if this behavior has changed in a recent release or not, but in
any case, using these commands with "-n" works.
Jerry
- Re: How to lock CVS for check-in, (continued)
- Re: How to lock CVS for check-in, Shubhabrata Sengupta, 2001/10/10
- Re: How to lock CVS for check-in, Shubhabrata Sengupta, 2001/10/11
- Re: How to lock CVS for check-in, Shubhabrata Sengupta, 2001/10/11
- RE: How to lock CVS for check-in, Pyatt, Scott, 2001/10/11
- RE: How to lock CVS for check-in, Pyatt, Scott, 2001/10/11
- Re: How to lock CVS for check-in, Shubhabrata Sengupta, 2001/10/11
- RE: How to lock CVS for check-in, Jerry Nairn, 2001/10/12
- RE: How to lock CVS for check-in,
Jerry Nairn <=