From: "Andy Fiddaman" <illumos@fiddaman.net>
To: illumos-developer <developer@lists.illumos.org>
Subject: Re: [developer] HEADS-UP: 16892 will definitively break building with gcc 4.4 primary
Date: Wed, 20 Nov 2024 05:25:40 -0500 [thread overview]
Message-ID: <17320983400.19E5.56082@composer.illumos.topicbox.com> (raw)
In-Reply-To: <4846c9eb-0ccd-4a31-b0a2-f3eeb1b9f1a0@haus-gisela.de>
[-- Attachment #1: Type: text/plain, Size: 563 bytes --]
On Wednesday, 20 November 2024, at 10:17 AM, Klaus Ziegler wrote:
> Andy, can I conntact you off list for details?
Of course, feel free.
It is fairly straightforward. If you choose import the 16892 change from illumos-gate, you will have to re-apply https://www.illumos.org/issues/13635 on top.
Andy
------------------------------------------
illumos: illumos-developer
Permalink: https://illumos.topicbox.com/groups/developer/Teb8715358214009f-M03caf0f14c08f371b529e4d7
Delivery options: https://illumos.topicbox.com/groups/developer/subscription
[-- Attachment #2: Type: text/html, Size: 1238 bytes --]
next prev parent reply other threads:[~2024-11-20 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 18:29 Andy Fiddaman
2024-11-20 10:17 ` Klaus Ziegler
2024-11-20 10:25 ` Andy Fiddaman [this message]
2024-11-20 10:52 ` Klaus Ziegler
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=17320983400.19E5.56082@composer.illumos.topicbox.com \
--to=illumos@fiddaman.net \
--cc=developer@lists.illumos.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 NNTP newsgroup(s).