From: dewar@gnat.com (Robert Dewar)
To: ac131313@redhat.com, jbuck@synopsys.com
Cc: binutils@sources.redhat.com, dj@redhat.com, gcc@gcc.gnu.org,
gdb@sources.redhat.com, mrs@apple.com, neroden@twcny.rr.com
Subject: Re: Libiberty license roundup (questions/potential problems)
Date: Wed, 28 May 2003 22:11:00 -0000 [thread overview]
Message-ID: <20030528221127.3FDE1F2D82@nile.gnat.com> (raw)
I have not seen any substantive argument for using other than the GPL here.
That's what would be useful.
next reply other threads:[~2003-05-28 22:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 22:11 Robert Dewar [this message]
2003-05-28 22:23 ` Joe Buck
-- strict thread matches above, loose matches on Subject: below --
2003-05-28 22:23 Robert Dewar
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
2003-05-30 18:59 ` DJ Delorie
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=20030528221127.3FDE1F2D82@nile.gnat.com \
--to=dewar@gnat.com \
--cc=ac131313@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=jbuck@synopsys.com \
--cc=mrs@apple.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).