Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Vladimir Prus <vladimir@codesourcery.com>,
	  "jakob@virtutech.com" <jakob@virtutech.com>,
	 "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: GDB MI Reverse Commands added [2 of 3]
Date: Fri, 12 Feb 2010 21:36:00 -0000	[thread overview]
Message-ID: <4B75C9C6.1090101@vmware.com> (raw)
In-Reply-To: <837hsl73up.fsf@gnu.org>

Eli Zaretskii wrote:
>> From: Vladimir Prus <vladimir@codesourcery.com>
>> Date: Wed, 16 Dec 2009 23:45:37 +0300
>> Cc: Michael Snyder <msnyder@vmware.com>,
>>  jakob@virtutech.com,
>>  gdb-patches@sourceware.org
>>
>> I am mildly concerned that the important high-level functionality is
>> only documented as option to specific commands, and as this functionality
>> is exercised and documentation is improved, we'll end up with information
>> scattered over N commands.
> 
> Ah, that's a valid concern.  How about if we do both: document the
> "--reverse" option with each command _and_ add a section with an
> overview of this feature?
> 
>> But let's wait and see -- right now, there's not so much information
>> there.
> 
> Agreed.
> 
> So the patch is clear to go in, as far as I'm concerned.

Checked in, after private email from Volodya.


  reply	other threads:[~2010-02-12 21:36 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-26 14:38 Jakob Engblom
2009-08-26 17:38 ` Eli Zaretskii
2009-08-27 13:48   ` Jakob Engblom
2009-08-28 10:05     ` Eli Zaretskii
2009-08-28 10:08   ` Jakob Engblom
2009-08-28 10:49     ` Eli Zaretskii
2009-08-28 13:41       ` Greg Law
2009-08-28 14:28         ` Eli Zaretskii
2009-08-28 17:12           ` Greg Law
2009-08-28 17:34             ` Eli Zaretskii
2009-08-28 18:49               ` Michael Snyder
2009-08-28 21:32                 ` Eli Zaretskii
2009-08-28 23:28                   ` Michael Snyder
2009-08-29  8:12                     ` Eli Zaretskii
2009-08-29 15:19                       ` Eli Zaretskii
2009-08-31 12:14                     ` Jakob Engblom
2009-08-31 13:06                       ` Jakob Engblom
2009-08-31 15:46                         ` Hui Zhu
2009-08-31 16:47                         ` Eli Zaretskii
2009-09-01  6:41                         ` Jakob Engblom
2009-12-15 19:41                         ` Michael Snyder
2009-12-16  8:01                           ` Vladimir Prus
2009-12-16 18:10                             ` Eli Zaretskii
2009-12-16 18:15                           ` Eli Zaretskii
2009-12-16 19:04                             ` Michael Snyder
2009-12-16 20:01                               ` Eli Zaretskii
2009-12-16 20:45                                 ` Vladimir Prus
2009-12-17 20:15                                   ` Eli Zaretskii
2010-02-12 21:36                                     ` Michael Snyder [this message]
2009-08-31 17:56                       ` Michael Snyder
2009-09-01  6:37                         ` Jakob Engblom
2009-08-29  7:37             ` Jakob Engblom
2009-08-28 10:44   ` Jakob Engblom

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=4B75C9C6.1090101@vmware.com \
    --to=msnyder@vmware.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jakob@virtutech.com \
    --cc=vladimir@codesourcery.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