From: "Arsen Arsenović" <arsen@aarsen.me>
To: Jan Beulich <jbeulich@suse.com>
Cc: Bruno Haible <bruno@clisp.org>, Iain Sandoe <iain@sandoe.co.uk>,
gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [PATCH v2 1/2] *: add modern gettext support
Date: Wed, 27 Sep 2023 15:06:41 +0200 [thread overview]
Message-ID: <86bkdnoj7r.fsf@aarsen.me> (raw)
In-Reply-To: <412429ef-152f-02d9-2c2f-a93e93e2a3bf@suse.com>
[-- Attachment #1: Type: text/plain, Size: 421 bytes --]
Jan Beulich <jbeulich@suse.com> writes:
> This looks sufficient to me, thanks. I don't feel qualified though to
> approve the binutils side of the change, sorry. I merely wanted to make
> sure there won't be sudden (and unmentioned) regressions as to where
> binutils can(not) be built.
It is important not to regress platform support, thank you for making
sure.
Have a lovely day!
--
Arsen Arsenović
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]
next prev parent reply other threads:[~2023-09-27 13:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 0:17 [PATCH v2 0/2] Replace intl/ with out-of-tree GNU gettext Arsen Arsenović
2023-09-26 0:17 ` [PATCH v2 1/2] *: add modern gettext support Arsen Arsenović
2023-09-26 2:12 ` Kevin Buettner
2023-09-26 5:09 ` Tsukasa OI
2023-09-26 8:58 ` Nick Clifton
2023-09-26 13:55 ` Arsen Arsenović
2023-09-26 7:03 ` Jan Beulich
2023-09-26 7:54 ` Iain Sandoe
2023-09-26 14:44 ` Arsen Arsenović
2023-09-27 7:11 ` Jan Beulich
2023-09-27 13:06 ` Arsen Arsenović [this message]
2023-09-27 15:19 ` Nick Clifton
2023-09-27 17:43 ` Arsen Arsenović
2023-09-28 9:43 ` Nick Clifton
2023-09-29 15:58 ` Bruno Haible
2023-09-29 16:27 ` Arsen Arsenović
2023-11-20 16:42 ` Kévin Le Gouguec
2023-11-20 20:30 ` Arsen Arsenović
2023-11-20 21:28 ` Bruno Haible
2023-09-26 0:17 ` [PATCH v2 2/2] *: suppress xgettext 0.22 charset name error Arsen Arsenović
2023-09-27 15:21 ` Nick Clifton
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=86bkdnoj7r.fsf@aarsen.me \
--to=arsen@aarsen.me \
--cc=binutils@sourceware.org \
--cc=bruno@clisp.org \
--cc=gdb-patches@sourceware.org \
--cc=iain@sandoe.co.uk \
--cc=jbeulich@suse.com \
/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).