From: Steve Nickolas <usotsuki@buric.co>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Early BSD license thread
Date: Wed, 21 Sep 2022 18:19:17 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.21.2209211817440.18088@sd-119843.dedibox.fr> (raw)
In-Reply-To: <CAEoi9W6WAe-bfqF7OUW55uy_vrja_BDY18pTntpJb0y=NEtMMA@mail.gmail.com>
On Wed, 21 Sep 2022, Dan Cross wrote:
> On Wed, Sep 21, 2022 at 5:50 PM Phil Budne <phil@ultimate.com> wrote:
>> Not to excuse the failure of the BSD team to properly attribute source
>> origin by adding only their copyright notice, but didn't AT&T try
>> unfair turnabout by not properly attributing the origins of their
>> TCP/IP code?
>
> One of my favorite copyright notices was for /bin/true in System V.
> An empty file got turned into 7 lines of comments holding copyright
> boilerplate and an `#ident` line with an SCCS version number:
> progress!
>
> - Dan C.
>
And then when I wrote it for my own project:
true -
#!/bin/sh
# Does something this small need a license? - SVN
exit 0
false -
#!/bin/sh
# Does something this small need a license? - SVN
exit 1
-uso.
next prev parent reply other threads:[~2022-09-21 22:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 10:10 [TUHS] " Warner Losh
2022-09-21 12:36 ` [TUHS] " Rob Pike
2022-09-21 13:33 ` Marc Donner
2022-09-21 13:46 ` Warner Losh
2022-09-21 14:50 ` Rich Salz
2022-09-21 14:58 ` Warner Losh
2022-09-21 15:06 ` Miod Vallat
2022-09-21 14:57 ` [TUHS] Fwd: " Clem Cole
2022-09-21 15:09 ` [TUHS] " Larry McVoy
2022-09-21 15:25 ` Warner Losh
2022-09-21 22:06 ` [TUHS] " Bakul Shah
2022-09-21 22:20 ` Warner Losh
2022-09-21 21:14 ` [TUHS] Re: Fwd: " Theodore Ts'o
2022-09-21 21:46 ` Clem Cole
2022-09-21 21:49 ` [TUHS] " Phil Budne
2022-09-21 22:07 ` Rich Salz
2022-09-21 22:24 ` Warner Losh
2022-09-21 22:09 ` Dan Cross
2022-09-21 22:19 ` Steve Nickolas [this message]
2022-09-21 22:44 ` Joseph Holsten
2022-09-21 23:53 ` Chet Ramey
2022-09-22 0:32 ` Rob Pike
2022-09-22 7:08 ` [TUHS] " Andy Kosela
2022-09-22 17:44 ` [TUHS] " Dan Cross
2022-09-22 18:44 ` Bakul Shah
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=alpine.DEB.2.21.2209211817440.18088@sd-119843.dedibox.fr \
--to=usotsuki@buric.co \
--cc=tuhs@tuhs.org \
/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).