From: Christian Biesinger <cbiesinger@google.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/2] Additional maintenance command for dumping target descriptions
Date: Thu, 11 Jun 2020 14:50:34 -0500 [thread overview]
Message-ID: <CAPTJ0XG+eXiJT-bButo4Qd36KWqB0DNDH2E8zc3y9t4Nz0QTpQ@mail.gmail.com> (raw)
In-Reply-To: <cover.1591871818.git.andrew.burgess@embecosm.com>
On Thu, Jun 11, 2020 at 5:41 AM Andrew Burgess
<andrew.burgess@embecosm.com> wrote:
> Patch #2 allows GDB developers to see in XML form the description that
> was sent from the target.
I haven't looked at the code but I've wanted that as well! Really
happy that you're working on this.
next prev parent reply other threads:[~2020-06-11 19:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 10:41 Andrew Burgess
2020-06-11 10:41 ` [PATCH 1/2] gdb: Allow target description to be dumped even when it is remote Andrew Burgess
2020-06-11 11:33 ` Pedro Alves
2020-06-11 14:05 ` Andrew Burgess
2020-06-11 14:24 ` Pedro Alves
2020-06-11 10:41 ` [PATCH 2/2] gdb: New maintenance command to print XML target description Andrew Burgess
2020-06-11 13:10 ` Pedro Alves
2020-06-11 13:27 ` Eli Zaretskii
2020-06-11 19:50 ` Christian Biesinger [this message]
2020-06-16 20:51 ` [PATCH 0/2] Additional maintenance command for dumping target descriptions Andrew Burgess
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=CAPTJ0XG+eXiJT-bButo4Qd36KWqB0DNDH2E8zc3y9t4Nz0QTpQ@mail.gmail.com \
--to=cbiesinger@google.com \
--cc=andrew.burgess@embecosm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).