From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: dberlin@dberlin.org, mec.gnu@mindspring.com
Cc: cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [commit/6.2] Fix lib (C)s; Was: src/gdb/testsuite ChangeLog lib/insight-suppor ...
Date: Tue, 20 Jul 2004 20:50:00 -0000 [thread overview]
Message-ID: <20040720205058.9555B4B104@berman.michael-chastain.com> (raw)
db> A phone book is very long, but not able to be protected at all
db> (Much to their chagrin :P).
db> The text quoted has to meet a set of requirements for originality, etc,
db> in order to be able to be protected.
db> I don't believe it does.
Okay, I see it would be hard to defend the FSF contact information
and the license terms as protectible.
But I'm concerned that the testsuite in particular has been very lax
in applying copyright notices, and I don't want people to think
"oh, it's just test code, it doesn't need a copyright notice".
Michael C
next reply other threads:[~2004-07-20 20:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-20 20:50 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-20 5:18 Michael Elizabeth Chastain
2004-07-20 17:34 ` Daniel Berlin
2004-07-19 22:33 Michael Elizabeth Chastain
2004-07-20 1:07 ` Andrew Cagney
2004-07-20 1:41 ` Daniel Berlin
2004-07-19 21:31 Michael Elizabeth Chastain
2004-07-19 21:58 ` Andrew Cagney
2004-07-17 20:36 Michael Elizabeth Chastain
2004-07-19 14:25 ` Andrew Cagney
2004-07-17 2:40 Michael Elizabeth Chastain
2004-07-17 2:56 ` Andrew Cagney
2004-07-14 20:46 Michael Elizabeth Chastain
2004-07-14 21:59 ` Martin M. Hunt
2004-07-17 2:09 ` [commit/6.2] Fix lib (C)s; Was: " Andrew Cagney
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=20040720205058.9555B4B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=dberlin@dberlin.org \
--cc=gdb-patches@sources.redhat.com \
/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