From: Siva Chandra <sivachandra@google.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Remove unused and probably incorrect macro TYPE_FN_FIELDS
Date: Wed, 16 Apr 2014 22:45:00 -0000 [thread overview]
Message-ID: <CAGyQ6gy8XnjoS5cj2LD9RLdOcxktTruFzu7cb=e4sh_vw7htVQ@mail.gmail.com> (raw)
In-Reply-To: <20140416153625.GV4250@adacore.com>
On Wed, Apr 16, 2014 at 8:36 AM, Joel Brobecker <brobecker@adacore.com> wrote:
>> 2014-04-16 Siva Chandra Reddy <sivachandra@google.com>
>>
>> * gdbtypes.h: Remove definition of the macro TYPE_FN_FIELDS.
>
> I'm not aware of the history either, but it's really easy to put back
> should there be any reason to, so go ahead and push.
Done, but with two pushes as I missed adding the ChangeLog entry in
the first push:
8000c58e455259951daa4370631aa616b367d1a7 and
7a23c5494be60600d34527f5adeaa2a34b85fdb6
prev parent reply other threads:[~2014-04-16 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 12:11 Siva Chandra
2014-04-16 15:36 ` Joel Brobecker
2014-04-16 22:45 ` Siva Chandra [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='CAGyQ6gy8XnjoS5cj2LD9RLdOcxktTruFzu7cb=e4sh_vw7htVQ@mail.gmail.com' \
--to=sivachandra@google.com \
--cc=brobecker@adacore.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