From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: dtaylor@emc.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Document short responses to qXfer:object:read.
Date: Fri, 27 May 2016 14:03:00 -0000 [thread overview]
Message-ID: <831t4n1tv8.fsf@gnu.org> (raw)
In-Reply-To: <8500ac65-6473-ec7b-9445-9e3bf6108f9a@redhat.com> (message from Pedro Alves on Fri, 27 May 2016 14:48:11 +0100)
> Cc: dtaylor@emc.com, gdb-patches@sourceware.org
> From: Pedro Alves <palves@redhat.com>
> Date: Fri, 27 May 2016 14:48:11 +0100
>
> I think that for symmetry, it be good to do the same to
> qxfer:object:write, even though the list of specific
> write requests isn't as large.
Done and pushed, thanks.
next prev parent reply other threads:[~2016-05-27 14:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 20:33 David Taylor
2016-05-27 8:35 ` Eli Zaretskii
2016-05-27 8:55 ` Pedro Alves
2016-05-27 13:21 ` Eli Zaretskii
2016-05-27 13:48 ` Pedro Alves
2016-05-27 14:03 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-27 16:52 David Taylor
2016-05-27 18:47 ` Eli Zaretskii
2016-05-26 18:11 David Taylor
2016-05-26 19:32 ` 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=831t4n1tv8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dtaylor@emc.com \
--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