From: Ian Lance Taylor <iant@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gcc-patches@gcc.gnu.org, binutils@sourceware.org,
gdb-patches@sourceware.org
Subject: Re: [gcc patch] Move ENUM_BITFIELD to ansidecl.h
Date: Mon, 25 Apr 2011 17:05:00 -0000 [thread overview]
Message-ID: <BANLkTikkdFLweQRE3Nhz1GDHPu_btmsnMw@mail.gmail.com> (raw)
In-Reply-To: <20110425060214.GA1786@host1.jankratochvil.net>
On Sun, Apr 24, 2011 at 11:02 PM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> include/
> 2011-04-25 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * ansidecl.h (ENUM_BITFIELD): New, from gcc/system.h.
>
> contrib/
> 2011-04-25 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * paranoia.cc (ENUM_BITFIELD): Remove.
>
> gcc/
> 2011-04-25 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * system.h (ENUM_BITFIELD): Remove.
>
> libcpp/
> 2011-04-25 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * system.h (ENUM_BITFIELD): Remove.
>
> ^^^ gcc approval
> ------------------------------------------------------------------------------
>
> for binutils part:
> include/
> 2011-04-25 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * bfdlink.h (ENUM_BITFIELD): Remove.
>
> gdb/
> 2011-04-25 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * defs.h (ENUM_BITFIELD): Remove.
This is OK.
Note that binutils/gdb include directory is copied from gcc directory,
so no separate approval is required there. But I technically can't
approve the change to gdb/defs.h, although I think it counts as
obvious given the other changes.
Thanks.
Ian
next prev parent reply other threads:[~2011-04-25 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 6:02 Jan Kratochvil
2011-04-25 17:05 ` Ian Lance Taylor [this message]
2011-04-25 18:15 ` Jan Kratochvil
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=BANLkTikkdFLweQRE3Nhz1GDHPu_btmsnMw@mail.gmail.com \
--to=iant@google.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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