From: "David O'Brien" <obrien@FreeBSD.org>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: gcc@gcc.gnu.org, gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: Libiberty license roundup (questions/potential problems)
Date: Fri, 30 May 2003 17:27:00 -0000 [thread overview]
Message-ID: <20030530172635.GC90937@dragon.nuxi.com> (raw)
In-Reply-To: <20030523225905.GA30461@doctormoo>
On Fri, May 23, 2003 at 06:59:05PM -0400, Nathanael Nerode wrote:
> The third are the BSD files with no explicit modification permission.
...
> (unusual, shorter version of the license, missing the "with
> or without modification" clause)
> strcasecmp.c
> strncasecmp.c
I can pull updated versions of these out of the BSD SCCS repo that has
more explicit copyrights.
--
-- David (obrien@FreeBSD.org)
next prev parent reply other threads:[~2003-05-30 17:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 22:59 Nathanael Nerode
2003-05-23 23:06 ` DJ Delorie
2003-05-23 23:59 ` Mike Stump
2003-05-24 1:23 ` Andrew Cagney
2003-05-24 1:34 ` DJ Delorie
2003-05-28 19:27 ` Andrew Cagney
2003-05-28 22:08 ` Joe Buck
2003-05-30 17:27 ` David O'Brien [this message]
2003-05-30 18:59 ` DJ Delorie
2003-05-28 22:11 Robert Dewar
2003-05-28 22:23 ` Joe Buck
2003-05-28 22:23 Robert Dewar
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=20030530172635.GC90937@dragon.nuxi.com \
--to=obrien@freebsd.org \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=neroden@twcny.rr.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).