From: Tom Tromey <tromey@redhat.com>
To: Cary Coutant <ccoutant@google.com>
Cc: Doug Evans <dje@google.com>,
gdb-patches <gdb-patches@sourceware.org>,
Sterling Augustine <saugustine@google.com>
Subject: Re: [patch] DWP V2 support
Date: Tue, 01 Oct 2013 15:08:00 -0000 [thread overview]
Message-ID: <87siwl81x2.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAHACq4piQt0tzG5ySj3YNB+=hRLzCSpb5nLzd4UggW8Kz_PU1w@mail.gmail.com> (Cary Coutant's message of "Mon, 30 Sep 2013 12:45:37 -0700")
>>>>> "Cary" == Cary Coutant <ccoutant@google.com> writes:
>> I suspect this is better placed in include/dwarf2.h.
>> Presumably some other tool needs this same enum.
Cary> Already there:
Perhaps it is already understood, but in this case the enum shouldn't
appear in this patch, on account of being redundant.
Tom
next prev parent reply other threads:[~2013-10-01 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 22:44 Doug Evans
2013-09-30 19:41 ` Tom Tromey
2013-09-30 19:45 ` Cary Coutant
2013-10-01 15:08 ` Tom Tromey [this message]
2013-10-05 2:14 ` Doug Evans
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=87siwl81x2.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=ccoutant@google.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=saugustine@google.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