From: Nick Clifton <nickc@redhat.com>
To: cgen@sources.redhat.com
Subject: RFC: Contributing the CGEN source to the FSF
Date: Wed, 11 Jul 2007 15:29:00 -0000 [thread overview]
Message-ID: <m3y7hnov4n.fsf@redhat.com> (raw)
Hi Guys,
I would like to have cgen sources contributed to the FSF. I am
prepared to do the work, but does anyone have any objections or
concerns ? If I can get agreement to the change then I will go
ahead with it as soon as possible.
One notable consequence of contributing the sources is that the
source license would change from GPL version 2 to GPL version 3, in
line with current FSF policy.
Another consequence would be that we could remove one of the cpu/
directories (either <toplevel>/cpu or <toplevel>/cgen/cpu, I am not
sure which would be better).
What do people think - is this a good idea ?
Cheers
Nick
PS. The impetus for this change has come from the FSF initiative to
change all of their projects sources over to the GPLv3 (or LGPLv3).
This includes both the binutils and GDB projects, so it would be
consistent if the cgen sources were changed over as well. (They do
not have to be, of course). So, if the cgen sources are going to
be changed to GPLv3 then why not contribute them at the same time ?
next reply other threads:[~2007-07-11 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 15:29 Nick Clifton [this message]
2007-07-13 3:03 ` Jim Blandy
2007-09-27 13:10 Doug Evans
2007-09-27 16:17 ` Nick Clifton
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=m3y7hnov4n.fsf@redhat.com \
--to=nickc@redhat.com \
--cc=cgen@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).