From: Mike Stump <mrs@apple.com>
To: Joseph S. Myers <joseph@codesourcery.com>
Cc: Nick Clifton <nickc@redhat.com>,
gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org,
binutils@sourceware.org
Subject: Re: Changing top level files and include/ files over to GPLv3
Date: Fri, 06 Jul 2007 20:51:00 -0000 [thread overview]
Message-ID: <9DB7619D-8F9F-4741-B968-D2000BD6F151@apple.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707062010110.1118@digraph.polyomino.org.uk>
On Jul 6, 2007, at 1:21 PM, Joseph S. Myers wrote:
> I do hope the FSF answer the backporting question
> <http://sourceware.org/ml/binutils/2007-07/msg00057.html> sooner
> rather
> than later.
I'd hope to have an answer to the backport question before we start
changing files. I'd hope that we'd change gcc first, then src. If
the FSF would just say, sure, you can drag fixes, patches and
improvements from the FSF gcc repository under GPLv3 back to GPLv2
vendor gcc release branches for the next year or two and those can be
released under the GPLv2, I think that would make things easier to
deal with. After two years, I'd expect that most of the vendors
would have cycled away from older compilers. However, some people,
like the embedded types can hang on to older compilers for longer
than you'd expect.
I'd look to the SC on guidance on when and how we start cutting over.
next prev parent reply other threads:[~2007-07-06 20:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 18:06 Nick Clifton
2007-07-06 18:25 ` Mark Kettenis
2007-07-06 18:34 ` Daniel Jacobowitz
2007-07-06 19:36 ` Joel Brobecker
2007-07-06 20:55 ` Daniel Jacobowitz
2007-07-09 9:47 ` Nick Clifton
2007-07-09 17:25 ` Joel Brobecker
2007-07-06 20:21 ` Joseph S. Myers
2007-07-06 20:31 ` DJ Delorie
2007-07-09 13:59 ` Alexandre Oliva
2007-07-06 20:51 ` Mike Stump [this message]
2007-07-06 21:11 ` Mark Mitchell
2007-07-09 13:23 ` Alexandre Oliva
2007-07-09 15:11 ` Gerald Pfeifer
2007-07-09 16:41 ` Alexandre Oliva
2007-07-09 17:06 ` Corinna Vinschen
2007-07-09 17:56 ` Alexandre Oliva
2007-07-09 19:45 ` Corinna Vinschen
2007-07-06 21:12 ` Russ Allbery
2007-07-11 1:56 ` Geoffrey Keating
2007-07-12 10:14 ` Nick Clifton
2007-07-12 10:16 ` Nick Clifton
2007-07-12 11:00 ` Geoffrey Keating
2007-07-12 11:30 ` Nick Clifton
2007-07-12 11:33 ` Andrew Haley
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=9DB7619D-8F9F-4741-B968-D2000BD6F151@apple.com \
--to=mrs@apple.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=joseph@codesourcery.com \
--cc=nickc@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