From: Jason Molenda <jason-swarelist@molenda.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: Adam Fedor <fedor@doc.com>, gdb <gdb@sources.redhat.com>
Subject: Re: Apple's Objective-C language patch
Date: Mon, 09 Sep 2002 23:21:00 -0000 [thread overview]
Message-ID: <20020909232030.A3483@molenda.com> (raw)
In-Reply-To: <3D7D7556.6010209@ges.redhat.com>; from ac131313@ges.redhat.com on Tue, Sep 10, 2002 at 12:30:14AM -0400
On Tue, Sep 10, 2002 at 12:30:14AM -0400, Andrew Cagney wrote:
> I know. and I believe this was was the likely intent. Just need to
> check that this is what Apple actually signed up to -> I need to ask a
> lawyer with the actual paper work in front of them to give a nod.
BTW, I can't answer the legal question here, but I can guarantee
you that the intention within Apple - understood by all our managers
- is to get as many of our changes into the FSF versions as possible.
Mostly they're not submitted because no one has time to fix them
and address issues raised by FSF maintainers. Some changes won't
ever go in because they're grody hacks, some won't go because
they're design decisions the FSF maintainers won't agree with.
But we derive no joy by hoarding our changes to gcc/gdb - share
and ejoy, I promise you that's the intention. Given that the
changes must be distributed under the GPL, and given our blanket
copyright assignment for changes to gcc/gdb, it's hard to imagine
how we could intend otherwise.
J
next prev parent reply other threads:[~2002-09-10 6:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-09 13:16 Adam Fedor
2002-09-09 17:34 ` Jason Molenda
2002-09-09 20:30 ` Adam Fedor
2002-09-09 20:49 ` Andrew Cagney
2002-09-09 20:55 ` Jason Molenda
2002-09-09 21:30 ` Andrew Cagney
2002-09-09 23:21 ` Jason Molenda [this message]
2002-09-09 20:58 ` Daniel Berlin
2002-09-09 21:00 ` Daniel Berlin
2002-09-11 9:03 ` Stan Shebs
2002-09-09 21:59 ` Jason Molenda
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=20020909232030.A3483@molenda.com \
--to=jason-swarelist@molenda.com \
--cc=ac131313@ges.redhat.com \
--cc=fedor@doc.com \
--cc=gdb@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