[Top][All Lists]

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

Re: Disabling -n option to commit/rtag

From: Joi Ellis
Subject: Re: Disabling -n option to commit/rtag
Date: Fri, 26 Apr 2002 15:36:24 -0500 (CDT)

On Fri, 26 Apr 2002 address@hidden wrote:

> > Ouch.  All I want to do is ensure that commitinfo is run for every commit,
> > and that taginfo is run for every tag.  There is no way to ensure this
> > (since a client using -n forces ignore of these files)?
> > 
> I don't understand here.  The -n flag means not to do anything, and
> therefore I don't see why commitinfo should be run.

cvs commit -n

-n is a common client option that says "don't run modules commands".

That's what the original poster wants to avoid.  I'd probably hack
the source and remove -n as a common client option.

This may cause more grief than just trusting the developers, tho.

> If you type
> cvs commit ...
> you are committing something, and the commitinfo will be run.
> If you type
> cvs -n commit ...

That's the common global -n, not the common client -n.

> then you aren't committing anything, just going through the motions,
> and no commitinfo should be run.
> Am I missing something?

Sort of. ;)

Joi Ellis                    Software Engineer
Aravox Technologies          address@hidden, address@hidden

No matter what we think of Linux versus FreeBSD, etc., the one thing I
really like about Linux is that it has Microsoft worried.  Anything
that kicks a monopoly in the pants has got to be good for something.
           - Chris Johnson

reply via email to

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