[Top][All Lists]

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

(no subject)

From: root
Subject: (no subject)
Date: Mon, 13 Aug 2001 05:19:58 -0400

>From address@hidden  Thu Feb 15 23:09:20 2001
>Return-Path: <address@hidden>
Received: from ( [])
        by (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id 
        for <address@hidden>; Thu, 15 Feb 2001 23:09:18 +0900
Received: from localhost ([]
        by with esmtp (Exim 3.16 #1 (Debian))
        id 14TP3B-0003Bb-00; Thu, 15 Feb 2001 09:06:25 -0500
Received: from ([]
        by with smtp (Exim 3.16 #1 (Debian))
        id 14TP2a-0003AG-00
        for <address@hidden>; Thu, 15 Feb 2001 09:05:48 -0500
Received: from ([])
          (InterMail v4.01.01.00 201-229-111) with SMTP
          id <address@hidden>
          for <address@hidden>; Thu, 15 Feb 2001 09:05:48 -0500
Reply-To: address@hidden
From: "Mark O'Brien" <address@hidden>
To: address@hidden
Received: from by
          via smtpd (for []) with SMTP; 15 Feb 
2001 13:58:22 UT
Subject: 2 "how to <> in CVS" questions
Message-ID: <address@hidden>
MIME-Version: 1.0
Content-Type: text/plain;
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: address@hidden
Errors-To: address@hidden
X-BeenThere: address@hidden
X-Mailman-Version: 2.0
Precedence: bulk
List-Help: <mailto:address@hidden>
List-Post: <mailto:address@hidden>
List-Subscribe: <>,
List-Id: Announcements and discussions for the CVS version control system 
List-Unsubscribe: <>,
List-Archive: <>
Date: Thu, 15 Feb 2001 09:06:20 -0500
Status: O
Content-Length: 1216
Lines: 35

Hello all.

I am trying to figure out how to implement an automated process in which,
just prior to checkin approval, the branch is verified. Then after checkin,
the bug number is attached to that new file version.

Any ideas or suggestions are greatly appreciated.

1. Given a bug number on checkin, CVS will query the bug tracking tool to
get the branch the bug is to be fixed in, check to see if the bug is in the
correct state, then CVS will validate the branch in the current checkin
operation is correct. This all would be done in the checkin pre-op trigger.

Question: How to implement the branch validation part.

2. If checkin is successful, the bug number should be somehow attached to
that new file version (not by the developer and we want to ensure the
validated bug from checkin is used).

Question: How could this be implemented in CVS?

3. In general, does anyone have any resource that describes how to automate
the baseline generation (add new versions for specified bug #'s on top of
previous baseline) for and automated build system in CVS?

Thanks all,


Info-cvs mailing list

reply via email to

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