From: Jason Molenda <jmolenda@apple.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: Huge Apple gdb code dropping^H^H^H^H
Date: Sun, 25 Nov 2001 09:42:00 -0000 [thread overview]
Message-ID: <FD4976A1-E511-11D5-B923-003065BC3540@apple.com> (raw)
In-Reply-To: <3C06A9C7.8070803@cygnus.com>
On Thursday, November 29, 2001, at 01:33 PM, Andrew Cagney wrote:
> Thanks! I'll figure out how to get it into the tree on some sort of
> branch.
You might want to wait for me to send in the current Apple sources. As
I noted, they don't work so well right now, but they are merged with the
latest FSF sources and they should be a little easier to wrangle into
shape if anyone is interested in doing so. (our local changes should be
nearly identical in both cases, they'll just be targeted to a more
recent gdb version)
BTW you'll obviously want to avoid a cvs import, or all our gdb-next/
directory will appear on the trunk.
> Andrew
> Card carrying memeber of the 3 button USB moose owners association.
Hm, I think someone's been up in The Great White North a little too
long...
Jason
WARNING: multiple messages have this Message-ID
From: Jason Molenda <jmolenda@apple.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: Huge Apple gdb code dropping^H^H^H^H
Date: Thu, 29 Nov 2001 13:43:00 -0000 [thread overview]
Message-ID: <FD4976A1-E511-11D5-B923-003065BC3540@apple.com> (raw)
Message-ID: <20011129134300.T-YG76x6l2LwxvXe5cC8zlLOWqsH6a4vGvDeAN-jSQg@z> (raw)
In-Reply-To: <3C06A9C7.8070803@cygnus.com>
On Thursday, November 29, 2001, at 01:33 PM, Andrew Cagney wrote:
> Thanks! I'll figure out how to get it into the tree on some sort of
> branch.
You might want to wait for me to send in the current Apple sources. As
I noted, they don't work so well right now, but they are merged with the
latest FSF sources and they should be a little easier to wrangle into
shape if anyone is interested in doing so. (our local changes should be
nearly identical in both cases, they'll just be targeted to a more
recent gdb version)
BTW you'll obviously want to avoid a cvs import, or all our gdb-next/
directory will appear on the trunk.
> Andrew
> Card carrying memeber of the 3 button USB moose owners association.
Hm, I think someone's been up in The Great White North a little too
long...
Jason
next prev parent reply other threads:[~2001-11-29 21:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Paul Hilfinger <hilfingr@gnat.com>
2001-11-29 0:59 ` Jason Molenda
2001-11-24 6:24 ` Jason Molenda
2001-11-25 0:39 ` Jason Molenda
2001-11-29 11:12 ` Jason Molenda
2001-11-29 13:34 ` Andrew Cagney
2001-11-25 9:41 ` Andrew Cagney
2001-11-25 9:42 ` Jason Molenda [this message]
2001-11-29 13:43 ` Jason Molenda
2001-11-25 9:47 ` Daniel Berlin
2001-11-29 14:15 ` Daniel Berlin
2001-11-29 7:29 ` David Relson
2001-11-24 12:36 ` David Relson
2001-11-29 10:27 ` Stan Shebs
2001-11-25 0:36 ` Stan Shebs
2001-11-29 11:25 ` Jason Molenda
2001-11-25 1:24 ` Jason Molenda
[not found] ` <200112070641.WAA01521@localhost.localdomain>
[not found] ` <3C10E0F3.2010607@cygnus.com>
2001-12-07 7:43 ` More code code dropping Andrew Cagney
2001-12-08 0:17 ` Paul Hilfinger
2001-12-08 7:56 ` Kevin Buettner
2001-12-08 11:05 ` David Relson
2001-12-08 15:27 ` Andrew Cagney
2001-12-13 5:27 ` Paul N. Hilfinger
2001-12-15 11:32 ` Andrew Cagney
2001-12-08 18:05 ` 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=FD4976A1-E511-11D5-B923-003065BC3540@apple.com \
--to=jmolenda@apple.com \
--cc=ac131313@cygnus.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