From: Pedro Alves <pedro@palves.net>
To: Tom de Vries <tdevries@suse.de>,
Simon Marchi <simon.marchi@polymtl.ca>,
gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/testsuite] Dump /proc/cpuinfo into gdb.log
Date: Fri, 24 Sep 2021 14:10:14 +0100 [thread overview]
Message-ID: <f5efccf9-19a3-17c3-f48f-a6ff9ead8f34@palves.net> (raw)
In-Reply-To: <76702685-e072-813e-07b5-9f3ab4878b94@suse.de>
On 2021-09-24 1:48 p.m., Tom de Vries wrote:
> Copied from mail, and done ... which also fixes the typo you reported.
>
> I'll commit this unless there are further comments.
>
No further comments from me, thanks.
prev parent reply other threads:[~2021-09-24 13:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 8:01 Tom de Vries via Gdb-patches
2021-09-23 14:32 ` Simon Marchi via Gdb-patches
2021-09-23 22:06 ` Tom de Vries via Gdb-patches
2021-09-24 12:21 ` Pedro Alves
2021-09-24 12:48 ` Tom de Vries via Gdb-patches
2021-09-24 13:10 ` Pedro Alves [this message]
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=f5efccf9-19a3-17c3-f48f-a6ff9ead8f34@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=tdevries@suse.de \
/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