From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: GDB 7.1 release planning...
Date: Fri, 08 Jan 2010 16:14:00 -0000 [thread overview]
Message-ID: <m38wc8zi9r.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100108135258.GA6814@caradoc.them.org> (Daniel Jacobowitz's message of "Fri, 8 Jan 2010 08:53:01 -0500")
>>>>> "Daniel" == Daniel Jacobowitz <dan@codesourcery.com> writes:
Daniel> On Fri, Jan 08, 2010 at 08:21:17AM +0400, Joel Brobecker wrote:
>> Is there anything that would be blocking for the branch creation?
>> There is a Wiki page for the gdb-7.1 release:
>>
>> http://sourceware.org/gdb/wiki/GDB_7.1_Release
Daniel> My two cents, since I'm not the one doing the work - but I received
Daniel> complaints that enough Python bits for the GTK filtered backtrace
Daniel> script were not in 7.0. How much has been merged since the 7.0
Daniel> release?
Not very much, mostly just bug fixes.
The filtered backtrace work is not fully baked yet. We know it is still
missing some needed features, at least.
Tom
next prev parent reply other threads:[~2010-01-08 16:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 4:21 Joel Brobecker
2010-01-08 9:24 ` Tristan Gingold
2010-01-08 11:08 ` Joel Brobecker
2010-01-08 13:49 ` Jan Kratochvil
2010-01-08 18:44 ` Michael Snyder
2010-01-09 3:08 ` Joel Brobecker
2010-01-08 13:53 ` Daniel Jacobowitz
2010-01-08 16:14 ` Tom Tromey [this message]
2010-01-09 3:18 ` Joel Brobecker
2010-01-11 19:58 ` Tom Tromey
2010-01-14 4:54 ` Joel Brobecker
2010-01-08 19:28 ` Stan Shebs
2010-01-08 22:32 ` Pedro Alves
2010-01-08 23:46 ` Stan Shebs
2010-01-09 3:31 ` Joel Brobecker
2010-01-09 16:52 ` Marc Khouzam
2010-01-11 9:48 ` Joel Brobecker
2010-01-11 14:31 ` Pedro Alves
2010-01-11 14:36 ` Pedro Alves
2010-01-13 23:17 ` Michael Snyder
2010-01-14 3:30 ` Joel Brobecker
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=m38wc8zi9r.fsf@fleche.redhat.com \
--to=tromey@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