From: Tom Tromey <tromey@adacore.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>,
Pedro Alves <pedro@palves.net>, Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH] Do not put linkage names into .gdb_index
Date: Mon, 25 Apr 2022 07:06:32 -0600 [thread overview]
Message-ID: <87y1ztpb1j.fsf@tromey.com> (raw)
In-Reply-To: <YmV37A9JcpX2Wpyo@adacore.com> (Joel Brobecker's message of "Sun, 24 Apr 2022 09:16:44 -0700")
Joel> Can we put that information as part of the comment directly in the
Joel> code? That way, someone looking for the "why" won't have to track
Joel> the commit all the way back to this email to get that piece of info.
Sure, I'll do that.
Tom
next prev parent reply other threads:[~2022-04-25 13:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 17:48 Tom Tromey
2022-04-22 18:02 ` Pedro Alves
2022-04-22 19:53 ` Tom Tromey
2022-04-22 19:55 ` Pedro Alves
2022-04-24 16:16 ` Joel Brobecker
2022-04-25 13:06 ` Tom Tromey [this message]
2022-04-25 9:42 ` George, Jini Susan
2022-04-25 13:07 ` Tom Tromey
2022-04-26 8:06 ` George, Jini Susan
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=87y1ztpb1j.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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).