From: Andreas Schwab <schwab@linux-m68k.org>
To: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
Cc: fweimer@redhat.com, Carlos O'Donell <carlos@redhat.com>
Subject: Re: [PATCH 2/2] localedata: Do not generate output if warnings were present.
Date: Thu, 17 Feb 2022 15:52:03 +0100 [thread overview]
Message-ID: <878ru9r1f0.fsf@igel.home> (raw)
In-Reply-To: <20220205025700.3728228-3-carlos@redhat.com> (Carlos O'Donell via Libc-alpha's message of "Fri, 4 Feb 2022 21:57:00 -0500")
On Feb 04 2022, Carlos O'Donell via Libc-alpha wrote:
> With LC_MONETARY parsing fixed we can now generate locales
> without forcing output with '-c'.
>
> Removing '-c' from localedef invocation is the equivalent of
> using -Werror for localedef. The glibc locale sources should
> always be clean and free from warnings.
>
> We remove '-c' from both test locale generation and the targets
> used for installing locales e.g. install-locale-archive, and
> install-locale-files.
>
> Tested on x86_64 and i686 without regressions.
> Tested with install-locale-archive target.
> Tested with install-locale-files target.
Ok.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2022-02-17 14:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 2:56 [PATCH 0/2] Improve LC_MONETARY handling Carlos O'Donell
2022-02-05 2:56 ` [PATCH 1/2] localedef: Update LC_MONETARY handling (Bug 28845) Carlos O'Donell
2022-02-08 3:46 ` DJ Delorie
2022-02-17 14:51 ` Andreas Schwab
2022-02-05 2:57 ` [PATCH 2/2] localedata: Do not generate output if warnings were present Carlos O'Donell
2022-02-08 3:51 ` DJ Delorie
2022-02-17 14:52 ` Andreas Schwab [this message]
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=878ru9r1f0.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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).