| Date Of Receipt: 12-AUG-1993 10:18:13.03
From: FLAMBE::jmf "Joshua M. Friedman ULTRIX SDE 12-Aug-1993 1017"
To: lynn@DEC:.zko.flambe
CC: [email protected], buildhelp@DEC:.zko.flambe, barrys@DEC:.zko.flambe
Subj: re: proprietary notices
Lynn, can you help here? If the standard @DEC_COPYRIGHT@ token is used
in the file, it'll get the standard copyright message. Do we have a
more-proprietary message than that (or should we)? How is a file tagged
as not going into the source kit? Do you maintain a list? Maybe we could
start a list which is in a file submitted into the pool, like:
./admin/proprietary_sources.list
-josh
------- Forwarded Message
Return-Path: [email protected]
Delivery-Date: Thu, 12 Aug 93 08:17:22 +28716
Return-Path: [email protected]
Received: by flambe.zk3.dec.com; id AA12553; Thu, 12 Aug 1993 08:17:20 -0400
Received: by abyss.zk3.dec.com (5.65/DEC-USSG-ZK3-ULTRIX-09/27/91);
id AA21966; Thu, 12 Aug 1993 08:17:06 -0400
Received: by mountain.zk3.dec.com; id AA12958; Thu, 12 Aug 1993 08:17:05 -0400
Date: Thu, 12 Aug 1993 08:17:05 -0400
From: John T Kohl <[email protected]>
Message-Id: <[email protected]>
To: [email protected]
Subject: proprietary notices
X-Us-Snail: DEC, 110 Spit Brook Road, M/S ZKO3-3/U14, Nashua, NH 03062
What do I need to do upon check-in and/or bsubmit to insure that a
new source file checked into one of the release pools will be:
(a) marked as Digital proprietary, and
(b) not shipped on a source kit
?
John
------- End of Forwarded Message
|