From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] gdbserver: rename source files to .cc
Date: Thu, 13 Feb 2020 14:05:00 -0000 [thread overview]
Message-ID: <87zhdmpoov.fsf@tromey.com> (raw)
In-Reply-To: <20200212225340.28865-2-simon.marchi@efficios.com> (Simon Marchi's message of "Wed, 12 Feb 2020 17:53:40 -0500")
>>>>> "Simon" == Simon Marchi <simon.marchi@efficios.com> writes:
Simon> For the same reasons outlined in the previous patch, this patch renames
Simon> gdbserver source files to .cc.
I support this as well, but I wonder if it would be easier for Tankut if
we held off landing this patch until his big target_ops series goes in.
Tom
next prev parent reply other threads:[~2020-02-13 14:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 22:54 [PATCH 1/2] gdbsupport: " Simon Marchi
2020-02-12 22:54 ` [PATCH 2/2] gdbserver: " Simon Marchi
2020-02-13 14:05 ` Tom Tromey [this message]
2020-02-13 14:48 ` Simon Marchi
2020-02-13 15:08 ` Tom Tromey
2020-02-13 15:28 ` Aktemur, Tankut Baris
2020-02-13 14:05 ` [PATCH 1/2] gdbsupport: " Tom Tromey
2020-02-13 14:41 ` Simon Marchi
2020-02-13 18:34 ` Pedro Alves
2020-02-13 21:22 ` Simon Marchi
2020-02-13 21:26 ` Pedro Alves
2020-02-13 21:31 ` Simon Marchi
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=87zhdmpoov.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.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