From: Vadim Antonov avg@postman.ncube.com
Subject: fixes
Date: Thu, 17 Aug 1995 07:32:29 -0400 [thread overview]
Message-ID: <19950817113229._DjxjCdQqTic1wy-EvUyno8oOs6nIto6NCiABarQ9SE@z> (raw)
>From the legal point of view posting "old lines" in
the diff and posting a single source file are identical,
and both are covered by "fair use", as in both cases
the "original bytes" are present and are useless without
the rest of the system. Even *names of files* can
be considered "violation", see also the text of USL's
complaint against BSD Inc.
Can somebody from Bell Labs explain their policy on
posting fixes and additions in the public mailing lists?
Just to put the discussion to the rest.
--vadim
next reply other threads:[~1995-08-17 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-08-17 11:32 Vadim [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-08-18 13:57 fixes Scott
1995-08-18 3:41 fixes dhog
1995-08-18 1:34 fixes Bruce
1995-08-18 1:02 fixes forsyth
1995-08-17 11:13 fixes Vadim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19950817113229._DjxjCdQqTic1wy-EvUyno8oOs6nIto6NCiABarQ9SE@z \
--to=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).