Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site pixel.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!panda!talcott!wjh12!pixel!vsh From: vsh@pixel.UUCP (vsh) Newsgroups: net.unix Subject: How to post upgrades to Unix sources Message-ID: <35@pixel.UUCP> Date: Fri, 1-Nov-85 13:54:20 EST Article-I.D.: pixel.35 Posted: Fri Nov 1 13:54:20 1985 Date-Received: Sun, 3-Nov-85 06:26:12 EST Organization: Pixel Systems Inc., Woburn, Mass. Lines: 23 I'm fairly new to all this, so: What is the correct (best) way to post upgrades/bug fixes to the net, especially when the original program is covered by copyright licenses with AT&T, UCB, etc. I recently posted an upgrade to sed using a "diff -e" generated ed script based on our AT&T System V, Release 2 master tape. Since the script contained only new code (insertions) and deletion/change instructions, I felt safe re. any copyright requirements. However, now I have being asked to post changes using "diff -c", providing context. In this case, significant sections of code (deleted from the original) will appear in the "diff -c" output. Are there any rules-of-thumb for making such postings?? Is Ma Bell going to stick me with noisy phone lines for the rest of my life? :-) To you Unix wizards familiar with these kinds of things, thanks in advance for your advice. -- Steve Harris | {allegra|ihnp4|cbosgd|ima|genrad|amd|harvard}\ Pixel Systems Inc. | !wjh12!pixel!vsh 300 Wildwood Street | Woburn, MA 01801 | 617-933-7735 x2314