Mark,
- Original Message -
From: "Mark O'Brien" [EMAIL PROTECTED]
Okay, here's what I would like to do.
Short: Create and automated baseline/build/package system, that executes
after being given bugs that have been fixed.
...
1) Need to have CVS ask for bug number prior to
Mark O'Brien wrote:
I didn't what to get into the why's of what I ask. But it is to automate the
SCM baseline/build/package process. See inline for more info below.
The problem is that people ask "How do I do this?" when it is
difficult or impossible to do exactly "this", or perhaps
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
David H. Thornley
Sent: Friday, February 16, 2001 11:41 AM
To: [EMAIL PROTECTED]
Subject: Re: 2 "how to in CVS" questions
Mark O'Brien wrote:
I didn't what to get into the why's of
Mark O'Brien wrote:
Okay, here's what I would like to do.
Short: Create and automated baseline/build/package system, that executes
after being given bugs that have been fixed.
Thanks. This makes things easier.
Detail:
1) Need to have CVS ask for bug number prior to checkin.
nley; info-cvs
Subject: RE: 2 "how to in CVS" questions
Okay, here's what I would like to do.
Short: Create and automated baseline/build/package system,
that executes
after being given bugs that have been fixed.
Detail:
1) Need to have CVS ask for bug number prior to
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
On Thu, Feb 15, 2001 at 09:06:20AM -0500, Mark O'Brien wrote:
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.
From reading your
