This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: ping: RFA: GPLv3: gcc/ada
On Aug 24, 2007, Arnaud Charlet <charlet@adacore.com> wrote:
> Because it will make it harder to most Ada developers (AdaCore people)
> to contribute their changes until we've solved these issues for
> our own version.
That's the bit I don't quite understand. How can it be that a patch
going into the FSF tree would make it harder for you to contribute
your changes?
I don't assume you keep your internal tree fully in sync with that of
gcc.gnu.org. At the very least, I assume you have local patches that
add vendor information or some such, and whatever you use to keep the
out of the merge process could be used to address license differences
as well. And then, since the bulk merges are from your tree to the
FSF, the license upgrade in the FSF tree wouldn't affect you at all.
So can please you explain what part of your internal development
process would become more difficult because of this trivial,
nearly-mechanical and out-of-the-code-path change in the FSF tree? I
honestly don't understand, and this makes it hard to find sympathy for
your needs.
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}