Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Snyder <msnyder@vmware.com>
Cc: pedro@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: [rfa] Use get_number_or_range for kill inferior etc.
Date: Sat, 26 Feb 2011 10:35:00 -0000	[thread overview]
Message-ID: <83mxljp9hu.fsf@gnu.org> (raw)
In-Reply-To: <4D683845.4010302@vmware.com>

> Date: Fri, 25 Feb 2011 15:16:21 -0800
> From: Michael Snyder <msnyder@vmware.com>
> CC: "pedro@codesourcery.com" <pedro@codesourcery.com>, 
>  "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
> 
> Eli Zaretskii wrote:
> >> Date: Fri, 25 Feb 2011 14:10:01 -0800
> >> From: Michael Snyder <msnyder@vmware.com>
> >> CC: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
> >>
> >> 2011-02-25  Michael Snyder  <msnyder@vmware.com>
> >>
> >> 	* gdb.texinfo (Inferiors and Programs): Update commands to show 
> >> 	that they can accept multiple arguments.
> > 
> > This part is OK, but I still think we should explain the syntax of
> > these "lists" in some place, and point to there in each of these
> > commands.
> 
> I think we all agree on that.

Then why doesn't this patch do something about that?  Maybe I'm
missing some related plan, if so apologies.


  reply	other threads:[~2011-02-26  6:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25 20:52 Michael Snyder
2011-02-25 21:45 ` Pedro Alves
2011-02-25 22:30   ` Michael Snyder
2011-02-25 23:16     ` Eli Zaretskii
2011-02-26  2:09       ` Michael Snyder
2011-02-26 10:35         ` Eli Zaretskii [this message]
2011-02-26 18:47           ` Michael Snyder
2011-02-26 19:52             ` Eli Zaretskii
2011-02-26 13:53     ` Pedro Alves
2011-02-27 20:57       ` Michael Snyder

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=83mxljp9hu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=pedro@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