From: Phil Muldoon <pmuldoon@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: make the GDB 7.2 release sooner?
Date: Thu, 27 May 2010 13:59:00 -0000 [thread overview]
Message-ID: <4BFE7AA2.3050708@redhat.com> (raw)
In-Reply-To: <20100527002906.GG20736@adacore.com>
On 05/27/2010 01:29 AM, Joel Brobecker wrote:
> What triggered this suggestion is python, but we do have lots of other
> things that are worth mentioning (in fact, everything in the NEWS files
> is worth mentioning), but to summarize:
The final "large" Python API patch was the py-inferior/py-infthread
stuff I submitted earlier this week. I'd really like to see that in
there and ship the next release of GDB as pretty much the API
equivalent (or as close as possible) to the Archer Python branch.
There are a few other API patches too, but they are minor and address
random bits of functionality. So if we can do this, and ship some of the
neat Python scripts in there too, that would be awesome!
Cheers
Phil
next prev parent reply other threads:[~2010-05-27 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 0:29 Joel Brobecker
2010-05-27 13:59 ` Phil Muldoon [this message]
2010-05-27 14:50 ` Joel Brobecker
2010-06-08 21:02 ` Tom Tromey
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=4BFE7AA2.3050708@redhat.com \
--to=pmuldoon@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
/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