From: "Arsen Arsenović" <arsen@aarsen.me>
To: Kevin Buettner <kevinb@redhat.com>
Cc: "Arsen Arsenović via Gdb-patches" <gdb-patches@sourceware.org>,
binutils@sourceware.org, "Iain Sandoe" <iain@sandoe.co.uk>,
"Bruno Haible" <bruno@clisp.org>
Subject: Re: [PATCH 0/2] Replace intl/ with out-of-tree GNU gettext
Date: Mon, 25 Sep 2023 21:43:39 +0200 [thread overview]
Message-ID: <861qemxcj8.fsf@aarsen.me> (raw)
In-Reply-To: <20230925121150.32d81bcf@f37-zws-nv>
[-- Attachment #1: Type: text/plain, Size: 813 bytes --]
Kevin Buettner <kevinb@redhat.com> writes:
> On Mon, 25 Sep 2023 17:13:39 +0200
> Arsen Arsenović via Gdb-patches <gdb-patches@sourceware.org> wrote:
>
>> Arsen Arsenović (2):
>> *: add modern gettext support
>> *: suppress xgettext 0.22 charset name error
>
> I haven't seen part 1, "add modern gettext support", in either email that
> I receive from the list(s) or in the public archives.
Yes, it was held for moderation due to size. It should be visible here:
https://inbox.sourceware.org/gdb-patches/20230925153247.908901-2-arsen@aarsen.me/
I'll send a v2 when the conversation under [PATCH 2/2] settles, and trim
that patch a bit (remove regenerated files) so that it fits under the
size limit.
Apologies for the inconvenience.
Have a lovely night!
--
Arsen Arsenović
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]
prev parent reply other threads:[~2023-09-25 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 15:13 Arsen Arsenović
2023-09-25 15:13 ` [PATCH 1/2] *: add modern gettext support Arsen Arsenović
2023-09-25 15:13 ` [PATCH 2/2] *: suppress xgettext 0.22 charset name error Arsen Arsenović
2023-09-25 15:46 ` Andreas Schwab
2023-09-25 15:55 ` Arsen Arsenović
2023-09-25 19:11 ` [PATCH 0/2] Replace intl/ with out-of-tree GNU gettext Kevin Buettner
2023-09-25 19:43 ` Arsen Arsenović [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=861qemxcj8.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=kevinb@redhat.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).