From: Joel Brobecker <brobecker@adacore.com>
To: Hans-Peter Nilsson <hp@bitrange.com>, gdb-patches@sourceware.org
Subject: Re: [commit/sim] Switch to GPLv3
Date: Mon, 27 Aug 2007 17:05:00 -0000 [thread overview]
Message-ID: <20070827170536.GA3652@adacore.com> (raw)
In-Reply-To: <20070826133313.GA18680@caradoc.them.org>
> Most of the remaining ones are not FSF copyrighted. I see only:
> sim/igen/lf.c
> mips/configure.ac
> testsuite/sim/mips/testutils.inc
> testsuite/sim/mips/utils-dsp.inc
> testsuite/sim/mips/utils-fpu.inc
> testsuite/sim/mips/utils-mdmx.inc
Oops, thanks to both of you for spotting these. I will fix these
files as soon as I have a moment - unless someone gets to them
before I do, of course ;-).
--
Joel
next prev parent reply other threads:[~2007-08-27 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070824143924.GA7612@adacore.com>
2007-08-26 12:43 ` Hans-Peter Nilsson
2007-08-26 13:33 ` Daniel Jacobowitz
2007-08-26 14:06 ` Hans-Peter Nilsson
2007-08-27 17:05 ` Joel Brobecker [this message]
2007-08-28 0:14 ` Joel Brobecker
2007-08-28 0:41 ` Hans-Peter Nilsson
2007-08-28 16:09 ` Joel Brobecker
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=20070827170536.GA3652@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=hp@bitrange.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