From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Rename common to gdbsupport
Date: Tue, 02 Jul 2019 17:35:00 -0000 [thread overview]
Message-ID: <871rz8mjrs.fsf@tromey.com> (raw)
In-Reply-To: <0f4a7879-faed-6bea-5693-3c55feefa261@redhat.com> (Pedro Alves's message of "Tue, 2 Jul 2019 16:10:52 +0100")
Pedro> Do you plan to rename the "common-*" files and adjust the COMMON in
Pedro> include guards? More like OOC, since leaving it as is is fine
Pedro> with me too. There are also a number of wiki references to common/,
Pedro> those would be nice to fix.
I haven't done any of those in my current series, but I can put it on my
to-do list.
Tom
next prev parent reply other threads:[~2019-07-02 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 20:19 Tom Tromey
2019-07-02 15:10 ` Pedro Alves
2019-07-02 17:35 ` Tom Tromey [this message]
2019-07-08 21:01 ` Tom Tromey
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=871rz8mjrs.fsf@tromey.com \
--to=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).