Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jason Molenda <jason-swarelist@molenda.com>
To: Keith Seitz <keiths@redhat.com>
Cc: Jim Ingham <jingham@apple.com>,
	Andrew Cagney <ac131313@redhat.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [patch rfa:doco rfc:NEWS] mi1 -> mi2; rm mi0
Date: Tue, 01 Oct 2002 23:25:00 -0000	[thread overview]
Message-ID: <20021001232339.A71134@molenda.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0210011604210.1527-100000@valrhona.uglyboxes.com>; from keiths@redhat.com on Tue, Oct 01, 2002 at 04:42:28PM -0700

On Tue, Oct 01, 2002 at 04:42:28PM -0700, Keith Seitz wrote:

> <devil's advocate>
>[...]
> Apple, who has done a lot of work on gdb and MI; no doubt fixed a lot of 
> stuff, but only managed to "submit" a giant distribution tarball of their 
> modified GDB. I wouldn't be too suprised if some thought that Apple was 
> taking advantage of the public's work. Mind you, I'm not saying that any 
> of this is true, but I wouldn't be suprised if some one reading this list 
> felt that way.
> </devil's advocate>


This is definitely off-topic and I should just let it go... But this
isn't a fair representation of reality.  I think Keith knows it, and
I think all the gdb folks who know Jim know it.  The gdb group at
Apple is not large and has had tremendous struggles to get gdb working
correctly for its developers on the MacOS X platform -- there has
been literally no time left over.  Apple management is very supportive
of moving our fixes, enhancements and changes to the FSF as much
as possible -- as anyone would sensibly be -- but it's a simple matter
of not having the time to make it happen so far.

As for the source dump, you know very well that Andrew asked for
that, and I provided it right away.  (Incidentally, I'm not one of
these hard-working Apple gdb programmers, and even I couldn't find
time to make up the original tarball until a weekend.)

I think you can see Apple's committment to working with the free
software community in gcc more easily -- we've got more people
working on the compiler there and it is an obvious priority to
participate in the compiler's development and enhancement.  The
compiler and debugger groups are under the same management
structure - they're clued in that this is a necessary way to 
operate in the long term.


Back in the day, Cygnus was periodically flamed for being evil
software hoarders by various unclueful people because we weren't
releasing our local changes in the timeframe or manner that the
flamers wanted us to.  Keith, you should know better.

Jason


  parent reply	other threads:[~2002-10-02  6:25 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1033404264.17743.ezmlm@sources.redhat.com>
2002-09-30 17:48 ` Jim Ingham
2002-10-01  9:29   ` Andrew Cagney
2002-10-01 10:34     ` Jim Ingham
2002-10-01 13:25       ` Andrew Cagney
2002-10-01 14:01         ` Jim Ingham
2002-10-01 15:10           ` Andrew Cagney
2002-10-01 15:46             ` Jim Ingham
2002-10-01 16:39               ` Keith Seitz
2002-10-01 17:45                 ` Jim Ingham
2002-10-02  7:58                   ` Keith Seitz
2002-10-02 10:49                     ` Jim Ingham
2002-10-25 14:48                       ` Andrew Cagney
2002-10-01 23:25                 ` Jason Molenda [this message]
2002-10-02 10:22                 ` Stan Shebs
     [not found] <1035593825.16489.ezmlm@sources.redhat.com>
2002-10-25 18:22 ` Jim Ingham
2002-09-29 11:14 Andrew Cagney
2002-09-29 12:55 ` Daniel Jacobowitz
2002-09-29 13:19   ` Andrew Cagney
2002-09-29 14:37     ` Daniel Jacobowitz
2002-09-29 14:46       ` Andrew Cagney
2002-09-29 21:55         ` Daniel Jacobowitz
2002-09-30  8:03           ` Andrew Cagney
2002-09-30  8:16             ` Daniel Jacobowitz
2002-09-30 15:06               ` Andrew Cagney
2002-09-30 15:36                 ` Daniel Jacobowitz
2002-09-29 22:01 ` Eli Zaretskii
2002-09-30 15:14   ` Andrew Cagney
2002-09-30 22:13     ` Eli Zaretskii
2002-10-01 14:26 ` Andrew Cagney

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=20021001232339.A71134@molenda.com \
    --to=jason-swarelist@molenda.com \
    --cc=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jingham@apple.com \
    --cc=keiths@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