From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/NEWS] Mention new feature "Ada tasking support"
Date: Wed, 22 Oct 2008 20:16:00 -0000 [thread overview]
Message-ID: <uod1ce694.fsf@gnu.org> (raw)
In-Reply-To: <20081022195702.GC3638@adacore.com>
> Date: Wed, 22 Oct 2008 12:57:02 -0700
> From: Joel Brobecker <brobecker@adacore.com>
>
> 2008-10-22 Joel Brobecker <brobecker@adacore.com>
>
> * NEWS: Add entry for new feature (Ada tasking support).
>
> OK to commit?
Yes, but...
> + info task TASK_NO
> + Print detailed information about task TASK_NO.
> + task
> + Print the ID of the current task.
> + task TASK_NO
> + Switch the context of debugging to task TASK_NO.
Is "task ID" the same as "TASK_NO"? If so, let's use a consistent
terminology: pick one of them and stick to it.
Thanks.
next prev parent reply other threads:[~2008-10-22 20:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 19:57 Joel Brobecker
2008-10-22 20:16 ` Eli Zaretskii [this message]
2008-10-22 20:18 ` Joel Brobecker
2008-10-22 21:11 ` Eli Zaretskii
2008-10-22 22:15 ` 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=uod1ce694.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