From: Eli Zaretskii <eliz@gnu.org>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 7/7] Documentation for qXfer:threads:read handle attribute
Date: Sun, 09 Apr 2017 08:09:00 -0000 [thread overview]
Message-ID: <831st2m27q.fsf@gnu.org> (raw)
In-Reply-To: <20170408230738.3b46b061@pinnacle.lan> (message from Kevin Buettner on Sat, 8 Apr 2017 23:07:38 -0700)
> Date: Sat, 8 Apr 2017 23:07:38 -0700
> From: Kevin Buettner <kevinb@redhat.com>
>
> gdb/doc/ChangeLog:
>
> * gdb.texinfo (qXfer:threads:read): Add documentation for handle
> attribute.
OK.
next prev parent reply other threads:[~2017-04-09 8:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-09 5:50 [PATCH v2 0/7] Thread handle to thread info mapping Kevin Buettner
2017-04-09 6:06 ` [PATCH v2 1/7] Add target method for converting thread handle to thread_info struct pointer Kevin Buettner
2017-05-05 3:26 ` Simon Marchi
2017-07-19 0:01 ` Kevin Buettner
2017-04-09 6:07 ` [PATCH v2 2/7] Add `thread_from_thread_handle' function to (Python) gdb module Kevin Buettner
2017-04-13 16:11 ` Phil Muldoon
2017-05-05 3:54 ` Simon Marchi
2017-04-09 6:07 ` [PATCH v2 4/7] Test case for gdb.thread_from_thread_handle Kevin Buettner
2017-05-05 5:19 ` Simon Marchi
2017-04-09 6:07 ` [PATCH v2 7/7] Documentation for qXfer:threads:read handle attribute Kevin Buettner
2017-04-09 8:09 ` Eli Zaretskii [this message]
2017-04-09 6:07 ` [PATCH v2 3/7] Documentation for gdb.thread_from_thread_handle Kevin Buettner
2017-05-05 4:01 ` Simon Marchi
2017-05-05 6:25 ` Eli Zaretskii
2017-07-19 0:13 ` Kevin Buettner
2017-04-09 6:07 ` [PATCH v2 6/7] Add thread_handle_to_thread_info support for remote targets Kevin Buettner
2017-05-06 2:28 ` Simon Marchi
2017-04-09 6:07 ` [PATCH v2 5/7] Add thread_db_notice_clone to gdbserver Kevin Buettner
2017-05-06 1:46 ` Simon Marchi
2017-04-20 0:19 ` [PATCH v2 0/7] Thread handle to thread info mapping Kevin Buettner
2017-04-26 17:46 ` Kevin Buettner
2017-05-03 18:32 ` Kevin Buettner
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=831st2m27q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.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