From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: nickc@redhat.com, brobecker@adacore.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 18:34:00 -0000 [thread overview]
Message-ID: <20070706183355.GA29794@caradoc.them.org> (raw)
In-Reply-To: <200707061825.l66IPDiI029226@brahms.sibelius.xs4all.nl>
On Fri, Jul 06, 2007 at 08:25:13PM +0200, Mark Kettenis wrote:
> GDB hasn't switched yet, but we have our own COPYING file in gdb/, so
> I suppose there's no real problem with this.
>
> Joel, are you planning to convert to GPLv3 before cutting the 6.7
> branch?
I would suggest before. I believe all GNU projects are supposed to do
it by the end of the month, and the release branch would definitely
have to change.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-07-06 18:34 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 [this message]
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
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=20070706183355.GA29794@caradoc.them.org \
--to=drow@false.org \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--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