From: Tom Tromey <tom@tromey.com>
To: Aaron Merey <amerey@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/1] Add debuginfod support to GDB
Date: Fri, 10 Jan 2020 18:43:00 -0000 [thread overview]
Message-ID: <87v9pjtana.fsf@tromey.com> (raw)
In-Reply-To: <CAJDtP-QtT9FrOXGrLhdJJJgBqFwdOTk_RVUx9a_QMCApJVzDuw@mail.gmail.com> (Aaron Merey's message of "Fri, 10 Jan 2020 11:46:02 -0500")
>>>>> "Aaron" == Aaron Merey <amerey@redhat.com> writes:
Aaron> Ok how about gdb/debuginfod-support.h then?
I think a .c file is more appropriate.
Tom
prev parent reply other threads:[~2020-01-10 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 3:48 Aaron Merey
2020-01-09 13:48 ` Eli Zaretskii
[not found] ` <87h814r6p4.fsf@tromey.com>
2020-01-09 22:41 ` Aaron Merey
2020-01-09 23:28 ` Christian Biesinger via gdb-patches
2020-01-10 16:32 ` Aaron Merey
[not found] ` <87tv53wfub.fsf@tromey.com>
2020-01-10 16:46 ` Aaron Merey
2020-01-10 18:43 ` Tom Tromey [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=87v9pjtana.fsf@tromey.com \
--to=tom@tromey.com \
--cc=amerey@redhat.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