public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bruce Korb <bkorb@gnu.org>
To: Rainer Orth <ro@cebitec.uni-bielefeld.de>
Cc: Mike Stump <mikestump@comcast.net>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [fixincludes] Fix macOS 10.12 <AvailabilityInternal.h> and <os/trace.h> (PR sanitizer/78267)
Date: Fri, 18 Nov 2016 17:23:00 -0000	[thread overview]
Message-ID: <CAKRnqNJYfYP-CciYQ+4dOGkm2EEhdGyYaC1Rg1fu_2AvdXw=ZA@mail.gmail.com> (raw)
In-Reply-To: <yddvavlkqwt.fsf@CeBiTec.Uni-Bielefeld.DE>

I think restoring bootstrap is likely a good thing.

On Fri, Nov 18, 2016 at 2:45 AM, Rainer Orth
<ro@cebitec.uni-bielefeld.de> wrote:
>
> I guess this is ok for mainline now to restore bootstrap?

  reply	other threads:[~2016-11-18 17:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11 10:15 Rainer Orth
2016-11-11 11:19 ` Mike Stump
2016-11-11 16:17   ` Iain Sandoe
2016-11-11 16:50     ` Rainer Orth
2016-11-11 16:58       ` Iain Sandoe
2016-11-11 17:01         ` Rainer Orth
2016-11-11 21:25   ` Bruce Korb
2016-11-18 10:45     ` Rainer Orth
2016-11-18 17:23       ` Bruce Korb [this message]
2016-11-18 17:42       ` Mike Stump
2016-11-18 19:25         ` Bruce Korb
2016-11-21  9:55           ` Rainer Orth
2016-11-21  9:52         ` Rainer Orth
     [not found] ` <CAJMcOU-k7qAJC9qpPo1ybTjWpsP7aEQGgZLwaOWomoVqMyMn8A@mail.gmail.com>
2016-11-13 10:53   ` Rainer Orth
     [not found]     ` <CAJMcOU93wuAXjLz7fRR1vRmgXn-BU7ajcOafxUWRfd1Rs4jk5g@mail.gmail.com>
2016-11-13 18:24       ` Fwd: " Jack Howarth
2016-11-14 14:11       ` Rainer Orth
2016-11-14 18:56         ` Jack Howarth
     [not found]       ` <CAJMcOU8m_8oCKpV4RD=1wo=PEs9fBcP52gyD1wtsO4B1v85dfQ@mail.gmail.com>
     [not found]         ` <5829b908.03a3620a.24461.716eSMTPIN_ADDED_MISSING@mx.google.com>
2016-11-14 13:19           ` Fwd: failure notice Jack Howarth
2016-11-14 14:22         ` [fixincludes] Fix macOS 10.12 <AvailabilityInternal.h> and <os/trace.h> (PR sanitizer/78267) Rainer Orth

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='CAKRnqNJYfYP-CciYQ+4dOGkm2EEhdGyYaC1Rg1fu_2AvdXw=ZA@mail.gmail.com' \
    --to=bkorb@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mikestump@comcast.net \
    --cc=ro@cebitec.uni-bielefeld.de \
    /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).