From: Mike Frysinger <vapier@gentoo.org>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: newlib@sourceware.org
Subject: Re: [PATCH] iconv: Fix EL/IX level 2 handling
Date: Sat, 19 Mar 2022 21:34:43 -0400 [thread overview]
Message-ID: <YjaEs2t13ea0kBC2@vapier> (raw)
In-Reply-To: <20220318155800.44208-1-sebastian.huber@embedded-brains.de>
[-- Attachment #1: Type: text/plain, Size: 459 bytes --]
On 18 Mar 2022 16:58, Sebastian Huber wrote:
> Consistently use
>
> if !ELIX_LEVEL_1
>
> to enable EL/IX level 2 interfaces.
based on the comments in the build, looks fine to me. i can't be bothered
to actually read the standards and EL/IX advice :).
one thing i noticed in the build is the various EL/IX variables are a bit
of a mess. i half debated standardizing the naming across the subdirs, but
obviously i gave up on that :).
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-03-20 1:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 15:58 Sebastian Huber
2022-03-20 1:34 ` Mike Frysinger [this message]
2022-03-22 6:20 ` Sebastian Huber
2022-03-22 15:13 ` Jeff Johnston
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=YjaEs2t13ea0kBC2@vapier \
--to=vapier@gentoo.org \
--cc=newlib@sourceware.org \
--cc=sebastian.huber@embedded-brains.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).