[Top][All Lists]

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

Re: hook into cvs AFTER tag?

From: Mark D. Baushke
Subject: Re: hook into cvs AFTER tag?
Date: Wed, 27 Apr 2005 11:21:48 -0700

Hash: SHA1

Michael Muller <address@hidden> writes:

> I have a "staging" sandbox that I would like to keep up-to-date with
> the versions of my files tagged as "release candidates" (tag name:
> "RC").
> My original plan was to put a command in the .taginfo file that does a
> "cvs update" in the staging sandbox (which was checked out with "-r
> RC").  This plan was foiled by the fact that .taginfo is called BEFORE
> the tagging occurs.
> Does anyone have any suggestion as to how I can perform some action
> server-side AFTER the tagging occcurs?
> I've had two ideas, both of which I don't like:
> 1) have .taginfo run something in the background that sleeps for some
> period that is longer than my tag command could ever take and then
> wakes up and updates the sandbox
> 2) have a cron job that updates the sandbox periodically
> I don't like either of these options because there's a delay and there
> is no user feedback when it's done.
> Does anyone have any better ideas?

If you can move from cvs 1.11.x (STABLE) to cvs 1.12.12 (FEATURE), then
you could make use of the "posttag" trigger.

I urge you to look very carefully at the administrative differences
between cvs 1.11.x and cvs 1.12.x releases and do lots of testing before
you make the choice. Although we try very hard to make both STABLE and
FEATURE work properly on all platforms, it is possible that you may find
problems that you need to address with your configuration and use of

> Thanks in advance,
>    -- Mike
> -- 
> Michael Muller
> Senior Application Developer, address@hidden, Inc.
> 2503 Walnut Street, Suite 301 Boulder, CO 80302
> phone: 303-442-1740
> fax:   303-442-1750
> This message is intended only for the use of the Addressee and may
> contain information that is PRIVILEGED and CONFIDENTIAL. If you are
> not the intended recipient, dissemination of this communication is
> prohibited. If you have received this communication in error, please
> erase all copies of the message and its attachments and notify us
> immediately.

You are hereby notified that communication to a subscription alias such
as address@hidden is NOT confidential as it is archived by many
different systems and is visible via Google and Yahoo! search engines as
well as others. Because of this, it is not possible to erase all copies
of this message.

If you need to use some kind of disclaimer for Sarbanes-Oxley, I suggest
you get your legal department involved in the real world to come up with
a disclaimer that makes sense when communicating with a public mailing
list. Failing that, I suggest you consider gettting a personal e-mail
address without those restrictions (eg, '' or '')
and use that for futher communications with address@hidden to avoid
trying to place any restrictions on the dissemination of your e-mail.

        -- Mark
Version: GnuPG v1.2.3 (FreeBSD)


reply via email to

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