[Top][All Lists]

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

Re: Precommitücheck question

From: Mark D. Baushke
Subject: Re: Precommitücheck question
Date: Mon, 13 Oct 2003 08:34:29 -0700

Hash: SHA1

Urban Gabor <address@hidden> writes:

> I would like to implement some preücommit check in the CVS,
> but I face some questions at the moment. Here thay are:

What version of cvs client and server are you using?

> 1. It seems, that cvs commit works differentr if I give the
> -m"blabla" option as the check-i comment. In this case CVS
> runs my script as intended, bat when I ommit the -m, and
> thus enter the comment in the editor, than the script is not
> running. Though the file is inserted properly in the
> commitinfo file.

The commitinfo script is called regardless of the use of -m"blabla" or
- -F"my-log-entry-file" ... 

In really old versions of cvs (1.9.x), the trigger that was used for
checking the log message was the editinfo trigger and it was bypassed
if -m"message" or -F"filename" was called. The verifymsg trigger was
added to always check the log message for the commit.

If I had to guess, I would say that the difference in triggers you are
seeing is related to the now deprecated editinfo trigger.

> 2. I would like the check the 'status' field of the prev.
> revesion before checking in the new revision. Is there an
> easy way the query the status?
> BTW I am running CVS on a Debian 2.0 box (CVS version 1.9.26).

This is very ancient. I urge you to consider updating to cvs 1.11.9.

However, for now if you are trying to run the 'cvs status' command
within one of the cvs triggers, you will need to add the '-n' switch as
in 'cvs -n status' in order to avoid running into a deadlock situation
of waiting to acquire a lock in a directory for which you already have a
write lock.

> Thanks id advance and regards,
> Gabaux
> Linux is like a wigwam: no gates, no windows, and an apache
> inside!

        Good luck,
        -- Mark
Version: GnuPG v1.2.3 (FreeBSD)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]