From: Nick Clifton <nickc@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>,
Mark Kettenis <mark.kettenis@xs4all.nl>,
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: Mon, 09 Jul 2007 09:47:00 -0000 [thread overview]
Message-ID: <4692042A.9090408@redhat.com> (raw)
In-Reply-To: <20070706205514.GA3923@caradoc.them.org>
> Joel Brobecker wrote:
>> Sounds good to me. I was getting ready to cut the branch this coming
>> sunday. This is going to be a massive change; will we be able to make
>> that conversion in time,
Sorry - the conversion was not made over the weekend. Mark Mitchell has
asked that the change over be held off until the discussion over what
happens to new patches (to GPLv3 sources) that want to be backported to
old branches (under GPLv2).
>> or should I start thinking about branching later?
If you can afford to wait then it would probably be a good thing. (On
the assumption that releasing under the GPLv3 is better than releasing
under GPLv2. At least for FSF projects anyway).
> Daniel Jacobwitz wrote:
> Might want to ask Nick how he did it. I'm not sure if there's any way
> better than by hand. But it shouldn't be too hard, just large...
By hand. :-) Directory edit mode in emacs plus several greps to make
sure that I had not missed anything. Tedious but not difficult.
Cheers
Nick
next prev parent reply other threads:[~2007-07-09 9:47 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 [this message]
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=4692042A.9090408@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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