From: Jeff Law <jeffreyalaw@gmail.com>
To: Iain Sandoe <iain@sandoe.co.uk>,
Nathanael Nerode <ncn_gcc10@fastmail.fm>
Cc: FX Coudert <fxcoudert@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Joseph Myers <joseph@codesourcery.com>,
"bonzini@gnu.org" <bonzini@gnu.org>,
neroden@gcc.gnu.org, aoliva@gcc.gnu.org, Ralf.Wildenhues@gmx.de
Subject: Re: Darwin: Replace environment runpath with embedded [PR88590]
Date: Sat, 21 Oct 2023 12:05:19 -0600 [thread overview]
Message-ID: <2a725c63-e4cb-4a59-af8d-c023f815db02@gmail.com> (raw)
In-Reply-To: <C64FC9CA-27EA-4193-9553-84F5A48E06F8@sandoe.co.uk>
On 10/8/23 16:14, Iain Sandoe wrote:
> + Jeff
>
>> On 8 Oct 2023, at 14:07, Nathanael Nerode <ncn_gcc10@fastmail.fm> wrote:
>>
>> I hope a global maintainer can step up. I've been on hiatus from GCC work for some years, and this was never my part of the build system anyway -- and I don't use Darwin -- so I'm not qualified to review it. It looks fine but it should be reviewed by someone who knows what they're doing.
>
> Thanks Nathanael for taking a look,
>
> @Jeff as we discussed at the Cauldron, I suspected it might be difficult to get this review, so would really appreciate if could cast an eye over it at some point,
If you could forward the remaining patches it'd be helpful. I think
Alex just acked one or more of these that affected the build machinery.
jeff
next prev parent reply other threads:[~2023-10-21 18:05 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 16:58 FX Coudert
2023-08-18 20:17 ` Joseph Myers
2023-08-18 22:31 ` Iain Sandoe
2023-08-18 22:59 ` Joseph Myers
2023-08-18 23:05 ` Iain Sandoe
2023-08-25 7:50 ` FX Coudert
2023-08-25 16:28 ` Joseph Myers
2023-08-29 16:06 ` FX Coudert
2023-08-29 19:55 ` Joseph Myers
2023-08-29 20:17 ` FX Coudert
2023-09-12 17:52 ` FX Coudert
2023-09-20 13:52 ` FX Coudert
2023-10-08 13:07 ` Nathanael Nerode
2023-10-08 22:14 ` Iain Sandoe
2023-10-21 18:05 ` Jeff Law [this message]
2023-10-21 18:26 ` Iain Sandoe
2023-10-21 5:27 ` Alexandre Oliva
2023-10-22 21:18 ` FX Coudert
2023-11-30 19:43 ` Ian Lance Taylor
2023-11-30 19:56 ` Iain Sandoe
2023-11-30 19:58 ` Ian Lance Taylor
2023-11-30 21:25 ` Ian Lance Taylor
2023-10-30 16:17 ` Martin Jambor
[not found] ` <653fd72a.050a0220.a6a20.de86SMTPIN_ADDED_BROKEN@mx.google.com>
2023-10-30 16:19 ` Iain Sandoe
2023-10-30 16:31 ` FX Coudert
2023-10-30 19:08 ` Iain Sandoe
2023-11-15 20:11 ` Thomas Schwinge
2023-11-15 20:34 ` FX Coudert
2023-11-17 11:56 ` FX Coudert
2023-11-17 12:13 ` Thomas Schwinge
2023-11-17 14:20 ` FX Coudert
2023-11-22 10:52 ` Iain Sandoe
2023-11-22 10:55 ` FX Coudert
2023-11-13 15:27 ` gfortran.dg/dg.exp debug messages pollute test output Rainer Orth
2023-11-13 16:19 ` Iain Sandoe
2023-11-15 10:29 ` FX Coudert
2023-11-15 12:04 ` Rainer Orth
2023-11-17 12:36 ` Thomas Schwinge
2023-11-18 9:03 ` FX Coudert
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=2a725c63-e4cb-4a59-af8d-c023f815db02@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=aoliva@gcc.gnu.org \
--cc=bonzini@gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
--cc=joseph@codesourcery.com \
--cc=ncn_gcc10@fastmail.fm \
--cc=neroden@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).