From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: GDB 7.2 release date
Date: Thu, 19 Aug 2010 19:11:00 -0000 [thread overview]
Message-ID: <201008192011.34957.pedro@codesourcery.com> (raw)
In-Reply-To: <20100819130952.GL2919@adacore.com>
On Thursday 19 August 2010 14:09:52, Joel Brobecker wrote:
> Following Stan's NEWS patch (thank you!), we should be pretty close to
> being ready for the 7.2 release. I propose to create it either Friday
> afternoon (UTC+2 - should be morning in the US), or sometime Monday if
> we find more blocking issues.
>
> BTW: I think that we're still missing NEWS entries for at least one
> feature that Pedro identified... I will try to help with those.
I just diffed 7.1 vs 7.2, and grepped for things like
grep "add_" ... | grep "cmd"
I've documented in the wiki the new commands that are missing an
entry in news or in the manual. Here's a copy of what I placed there:
* Missing in NEWS:
o [Stan]: Tracepoint source strings, observer mode, corresponding commands and packets. $_thread.
http://sourceware.org/ml/gdb-patches/2010-08/msg00325.html
o [Joel]: $_thread.
http://sourceware.org/ml/gdb-patches/2010-08/msg00353.html
o set|show record memory-query.
* Missing in NEWS and manual:
o record pic
o set|show record pic
o set record pic hide-nofunction
o set record pic hide-nosource
o set record pic hide-sameaddr
o set record pic type
[Hui]: http://sourceware.org/ml/gdb-patches/2010-07/msg00033.html
It appeared to me that for most commands and features there are already
patches pending, except for "set|show record memory-query", if I'm not mistaken.
Hui, what's the status of that patch?
I've also diffed remote.c in both trees, and confirmed that all new
packets are either already mentioned in NEWS, or the patches pointed at
above already take care of mentioning them.
Joel, I think you missed that Stan had already documented $_thread
in his patch. I've no idea if both descriptions could be merged so
we end up with a better description, or whether one of them ends
up redundant.
--
Pedro Alves
next prev parent reply other threads:[~2010-08-19 19:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 17:50 Joel Brobecker
2010-07-28 18:02 ` Pedro Alves
2010-07-28 22:02 ` Joel Brobecker
2010-07-29 14:14 ` Pedro Alves
2010-08-16 15:15 ` Joel Brobecker
2010-08-16 15:21 ` Pedro Alves
2010-08-16 16:01 ` Stan Shebs
2010-08-16 19:17 ` Joel Brobecker
2010-08-16 19:47 ` Pedro Alves
2010-08-18 20:13 ` Joel Brobecker
2010-08-18 21:50 ` Stan Shebs
2010-08-16 15:53 ` Mathew Yeates
2010-08-16 19:32 ` Joel Brobecker
2010-08-16 20:07 ` Tom Tromey
2010-08-16 20:19 ` Mathew Yeates
2010-08-16 20:23 ` Tom Tromey
2010-08-16 20:30 ` Mathew Yeates
2010-08-16 20:50 ` Tom Tromey
2010-08-16 21:30 ` Mathew Yeates
2010-08-02 17:00 ` Michael Snyder
2010-08-02 17:27 ` Joel Brobecker
2010-08-02 17:37 ` Jack Howarth
2010-08-02 17:40 ` Joel Brobecker
2010-08-02 18:17 ` Jack Howarth
2010-08-04 22:53 ` Michael Snyder
2010-08-19 13:10 ` Joel Brobecker
2010-08-19 19:11 ` Pedro Alves [this message]
2010-08-20 8:56 ` Joel Brobecker
2010-08-20 9:03 ` Joel Brobecker
2010-08-20 9:24 ` Eli Zaretskii
2010-08-22 9:34 ` 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=201008192011.34957.pedro@codesourcery.com \
--to=pedro@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).