From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/5] gdb/doc: Clarify vCont packet description
Date: Wed, 17 Feb 2016 15:56:00 -0000 [thread overview]
Message-ID: <831t8bwcsc.fsf@gnu.org> (raw)
In-Reply-To: <1455677091-13683-4-git-send-email-palves@redhat.com> (message from Pedro Alves on Wed, 17 Feb 2016 02:44:49 +0000)
> From: Pedro Alves <palves@redhat.com>
> Date: Wed, 17 Feb 2016 02:44:49 +0000
>
> gdb/doc/ChangeLog:
> 2016-02-16 Pedro Alves <palves@redhat.com>
>
> * gdb.texinfo (Packets): Clarify vCont packets with multiple
> actions that match a thread, and what happens when an action
> matches a thread that is already running.
OK, thanks.
next prev parent reply other threads:[~2016-02-17 15:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 2:44 [PATCH 0/5] Coalesce/aggregate (async) vCont packets/actions Pedro Alves
2016-02-17 2:44 ` [PATCH 3/5] gdb/doc: Clarify vCont packet description Pedro Alves
2016-02-17 15:56 ` Eli Zaretskii [this message]
2016-02-17 2:44 ` [PATCH 2/5] gdb: Free inferior->priv when inferior exits Pedro Alves
2016-02-17 2:44 ` [PATCH 1/5] gdb: Clean up remote.c:remote_resume Pedro Alves
2016-02-17 11:45 ` Luis Machado
2016-02-17 12:32 ` Pedro Alves
2016-02-17 13:44 ` Luis Machado
2016-02-17 2:51 ` [PATCH 5/5] gdb: Coalesce/aggregate (async) vCont packets/actions Pedro Alves
2016-02-17 13:42 ` Luis Machado
2016-10-26 15:35 ` Pedro Alves
2016-02-17 2:51 ` [PATCH 4/5] gdbserver: Leave already-vCont-resumed threads as they were Pedro Alves
2016-02-17 11:46 ` Luis Machado
2016-02-17 12:32 ` Pedro Alves
2016-10-26 15:39 ` Pedro Alves
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=831t8bwcsc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@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