[449] in Release_Engineering
[Re: text of public-cluster printer burst page needs to be updated ]
daemon@ATHENA.MIT.EDU (Henry Mensch)
Thu Oct 13 11:21:50 1988
To: rel-eng@ATHENA.MIT.EDU
Cc: beth@ATHENA.MIT.EDU, paul@ATHENA.MIT.EDU
Date: Thu, 13 Oct 88 11:21:12 EDT
From: Henry Mensch <henry@GARP.MIT.EDU>
i believe that beth and paul worked out a new burst page. please
insure this is checked into the sources ... thanks.
------- Forwarded Message
Received: by E40-PO.MIT.EDU (5.45/4.7) id AA10122; Mon, 19 Sep 88 13:00:07 EDT
Received: by ATHENA.MIT.EDU (5.45/4.7) id AA09760; Mon, 19 Sep 88 12:56:40 EDT
Received: by KLEE.MIT.EDU (5.45/4.7) id AA06182; Mon, 19 Sep 88 12:56:27 EDT
Message-Id: <8809191656.AA06182@KLEE.MIT.EDU>
To: Henry Mensch <henry@ATHENA.MIT.EDU>
Cc: <beth@ATHENA.MIT.EDU>, bugs@ATHENA.MIT.EDU, cfyi@ATHENA.MIT.EDU,
beth@ATHENA.MIT.EDU
Subject: Re: text of public-cluster printer burst page needs to be updated
In-Reply-To: Your message of Fri, 16 Sep 88 20:06:37 -0400.
<8809170006.AA12075@GARP.MIT.EDU>
Date: Mon, 19 Sep 88 12:56:22 EDT
From: Beth Anderson (Consulting Manager) <beth@ATHENA.MIT.EDU>
As I understand it from Jeff, the text of the burst page is stored
on the print servers.
As some day creating print servers is supposed to be a push-button
operations, I assume this text, which is stored in a file, would
need to be considered part of the release.
This is not a documentation problem, but a text-file-on-the-print-server
problem.
- -- Beth
------- End of Forwarded Message
