Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, brobecker@adacore.com
Subject: Re: [PATCH 3/3] [Ada/doco] Document the new -ada-task-info GDB/MI command.
Date: Sat, 17 Sep 2011 07:02:00 -0000	[thread overview]
Message-ID: <838vpnvf9m.fsf@gnu.org> (raw)
In-Reply-To: <1316201377-14830-4-git-send-email-brobecker@adacore.com>

> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Joel Brobecker <brobecker@adacore.com>
> Date: Fri, 16 Sep 2011 12:29:37 -0700
> 
> +@item state
> +The current state of the task.

Would it be a good idea to enumerate the possible states here?  Or is
that common knowledge for anyone who is an Ada programmer?

> +@smallexample
> +-thread-info
> +^done,tasks=@{nr_rows="3",nr_cols="8",

You are documenting -ada-task-info, so why the example is for a
different command?

> +@item ada-task-info
> +Indicates the presence of the @code{-ada-task-info} command.

I would use "availability of" or "support for", rather than "presence
of".  (Yes, I know the other items use the same language you did; I
think they all should be changed.)

Thanks.


  reply	other threads:[~2011-09-17  6:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1316201377-14830-1-git-send-email-brobecker@adacore.com>
2011-09-16 19:30 ` [PATCH 2/3] [Ada] Add field "thread-id" in -ada-task-info output Joel Brobecker
2011-09-16 19:30 ` [PATCH 1/3] [Ada] New GDB/MI command: -ada-tasks-info Joel Brobecker
2011-09-16 20:45   ` Joel Brobecker
2011-09-16 20:27 ` [PATCH 3/3] [Ada/doco] Document the new -ada-task-info GDB/MI command Joel Brobecker
2011-09-17  7:02   ` Eli Zaretskii [this message]
2011-09-19 18:57     ` Joel Brobecker
2011-10-03 21:41       ` Joel Brobecker
2011-09-16 20:45 [GDB/MI Ada] New GDB/MI command: -ada-tasks-info Joel Brobecker
2011-09-16 20:46 ` [PATCH 3/3] [Ada/doco] Document the new -ada-task-info GDB/MI command Joel Brobecker
2011-09-17  8:59   ` Eli Zaretskii

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=838vpnvf9m.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@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