From: doug@cs.dartmouth.edu (Doug McIlroy)
Subject: [TUHS] GNU vs BSD before the lawsuit and before Linux
Date: Sat, 18 Mar 2017 12:25:52 -0400 [thread overview]
Message-ID: <201703181625.v2IGPq1X066486@tahoe.cs.Dartmouth.EDU> (raw)
In-Reply-To: <CANCZdfrrhLa63sK92zc+cR4KZ6p=O1AzCjrTeO5Wp=4qr8eA5g@mail.gmail.com>
Nick asked for an exmple of AT&T code in Gnu.
Warner explained a spectrum of ways and degrees of innocence
by which that might happen.
The example I have in mind is "calendar" from v7, whose very
idiosyncratic implementation appeared in Gnu with only
cosmetic changes. It has been modified since by discarding
archaic efficiency hacks, but still uses the same quirky
basic method.
Conceivably Gnu's implementation was done only after v7
code was made public. But in any event, it has been
distributed without attribution.
Doug
next prev parent reply other threads:[~2017-03-18 16:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 13:07 Doug McIlroy
2017-03-18 13:27 ` Nick Downing
2017-03-18 15:19 ` Warner Losh
2017-03-18 16:25 ` Doug McIlroy [this message]
2017-03-18 17:45 ` Random832
2017-03-18 19:23 ` Warner Losh
-- strict thread matches above, loose matches on Subject: below --
2017-03-18 12:45 Doug McIlroy
2017-03-14 14:43 [TUHS] System Economics (was is Linux "officially branded UNIX") Clem Cole
2017-03-14 15:38 ` Larry McVoy
2017-03-14 15:51 ` Arthur Krewat
2017-03-14 15:57 ` Michael Kjörling
2017-03-14 16:20 ` Arthur Krewat
2017-03-14 18:41 ` Warner Losh
2017-03-17 18:16 ` [TUHS] GNU vs BSD before the lawsuit and before Linux Tony Finch
2017-03-17 18:52 ` Jeremy C. Reed
2017-03-19 7:18 ` arnold
2017-03-19 9:05 ` Wesley Parish
2017-03-19 18:37 ` Warner Losh
2017-03-17 19:54 ` Ron Natalie
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=201703181625.v2IGPq1X066486@tahoe.cs.Dartmouth.EDU \
--to=doug@cs.dartmouth.edu \
/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).