From: Junio C Hamano <gitster@pobox.com>
To: Han Young <hanyang.tony@bytedance.com>
Cc: Collin Funk <collin.funk1@gmail.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
git@vger.kernel.org, Taylor Blau <me@ttaylorr.com>
Subject: Re: [External] Re: [PATCH 0/1] Filter C and POSIX out of Accept-Language
Date: Fri, 11 Jul 2025 09:46:32 -0700 [thread overview]
Message-ID: <xmqq5xfy3cbb.fsf@gitster.g> (raw)
In-Reply-To: <CAG1j3zGn5fS=_Oftu7bBmWsoMc-aCa84AtDXdfxgL8QFEkp+yA@mail.gmail.com> (Han Young's message of "Fri, 11 Jul 2025 10:49:03 +0800")
Han Young <hanyang.tony@bytedance.com> writes:
>> But as you mentioned converting them would require a database of all
>> tags...
>
> Hardcoding all the locale names in the code should be fine, I guess?
That is exactly the "database" we do not want to have to maintain,
so not fine.
> Though the problem of filtering out locales unsupported by glibc is more
> troublesome.
prev parent reply other threads:[~2025-07-11 16:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 22:16 [PATCH 0/1] Filter C and POSIX out of Accept-Language brian m. carlson
2025-07-10 22:16 ` [PATCH 1/1] http: don't send C or POSIX in Accept-Language brian m. carlson
2025-07-10 22:47 ` Junio C Hamano
2025-07-10 23:08 ` brian m. carlson
2025-07-11 15:23 ` Justin Tobler
2025-07-11 17:02 ` Collin Funk
2025-07-11 20:57 ` Carlo Marcelo Arenas Belón
2025-07-11 21:29 ` brian m. carlson
2025-07-11 22:12 ` Carlo Arenas
2025-07-11 22:17 ` Collin Funk
2025-07-11 18:32 ` Junio C Hamano
2025-07-11 20:22 ` Carlo Marcelo Arenas Belón
2025-07-15 4:38 ` Eli Schwartz
2025-07-10 22:45 ` [PATCH 0/1] Filter C and POSIX out of Accept-Language Junio C Hamano
2025-07-10 23:08 ` brian m. carlson
2025-07-10 23:26 ` Collin Funk
2025-07-11 2:49 ` [External] " Han Young
2025-07-11 16:46 ` Junio C Hamano [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=xmqq5xfy3cbb.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=collin.funk1@gmail.com \
--cc=git@vger.kernel.org \
--cc=hanyang.tony@bytedance.com \
--cc=me@ttaylorr.com \
--cc=sandals@crustytoothpaste.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.