| Date Of Receipt: 11-NOV-1996 12:18:58.49
From: FLUME::"[email protected]" "11-Nov-1996 1215"
To: wolfson@dec:.zko.smurf (Kathy Wolfson, UNIX Sys. Release Eng.,DTN 381-6108)
CC: [email protected]
Subj: Re: Fewer buildmessages for ase & tcr
We'll take that as a tools enhancement request.: -)
The reason they come out that way is mostly historical. There are multiple
tools, some of which run asyncronously, that each forward their status at
various times. We've discussed changing the content and distribution of these
various messages
Which of these do you find useful and which could you do without? And as long
as I've opened the door, anybody else on odehelp that has an opinion, please
speak up.
-Grant
| Why don't the ase and tcr build messages include the additional build status
| messages. e.g., messages with the following headings:
|
| - ASE13SUPPORTOS: Build Status (GOOD)
| - ok ase13supportos.bld backingtree log
|
|
| Example, here are all the ase build messages since Nov. 7:
|
| # From Date Subject
|
| 1 MUDRAT::"[email protected] 7-NOV-1996 ase13supportos.nightly update in progres
| 2 MUDRAT::"[email protected] 7-NOV-1996 ase13supportos.nightly update completed
| 3 MUDRAT::"devbld@zk3. 7-NOV-1996 ASE13SUPPORTDX - X11 NIGHTLY build was s
| 4 MUDRAT::"[email protected] 7-NOV-1996 ase13supportos.nightly update in progres
| 5 MUDRAT::"[email protected] 7-NOV-1996 ase13supportos.nightly update completed
| 6 MUDRAT::"[email protected] 10-NOV-1996 ase12asupportos.nightly update in progre
| 7 MUDRAT::"[email protected] 10-NOV-1996 ase12asupportos.nightly update completed
|
|
| - Kathy
|
|
|