[Top][All Lists]

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

Re: CVS commitinfo

From: Larry Jones
Subject: Re: CVS commitinfo
Date: Wed, 17 Apr 2002 14:59:23 -0400 (EDT)

Eric Fried writes:
> This is a multi-part message in MIME format.

Please do not send MIME and/or HTML encrypted messages to the list. 
Plain text only, PLEASE!

> I just started trying to work with some of the admin features in CVS;
> particularly with commitinfo.  I am trying to write a validation script
> which will compile code prior to allowing commits.  Running into some
> snags;
>             a) Where are the working copies of the file?

In the current directory.

>             b) During the commit, the module dir is locked.
>                 From some other threads, noticed some others had this =
> problem.  From the repository
>                 path, I parse out the module name.  I then try to check =
> out the module for a test compile
>                 before allowing the commit.  The command hangs as the =
> rep. is now locked.  Anyway around
>                 this (aside from removing the the lock files from the =
> dir)?

No.  For some subcommands, you can use the global -n flag to ignore
locks, but not with checkout.  And note that removing the lock files is
an excruciatingly bad idea.  (Unless, of course, you *like* corrupted

-Larry Jones

Why is it you always rip your pants on the day everyone has to
demonstrate a math problem at the chalkboard? -- Calvin

reply via email to

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