[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CVS commitinfo trigger question
From: |
Pierre Asselin |
Subject: |
Re: CVS commitinfo trigger question |
Date: |
30 Nov 2001 20:00:03 -0600 |
"Bill Buie" <address@hidden> writes:
>I want to use a commitinfo trigger that will require a script of my =
>design to complete with zero status before permitting checkins to =
>certain branches. The most obvious way to tell what branch a file is =
>being committed to would be with the cvs status subcommand, but I have =
>run into a catch. The cvs commit subcommand locks the repository such =
>that the commitinfo script hangs when it tried to invoke the cvs status =
>subcommand.
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 Newsgroup Service in the World!
-----== Over 80,000 Newsgroups - 16 Different Servers! =-----