public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug locale/16621] C.UTF-8 locales should be regarded like C w.r.t. $LANGUAGE precedence
Date: Sun, 30 Aug 2015 05:59:00 -0000	[thread overview]
Message-ID: <bug-16621-131-391CMJXQpR@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16621-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=16621

--- Comment #6 from Mike Frysinger <vapier at gentoo dot org> ---
(In reply to Nick Coghlan from comment #5)

bugs in distros aren't really the domain of glibc upstream.  if you think the
proposal in bug 17318 has limitations or you have concerns, you should post it
there or the mailing list thread on the topic.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-08-30  5:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21 12:47 [Bug libc/16621] New: " vincent-srcware at vinc17 dot net
2014-02-21 13:41 ` [Bug libc/16621] " vincent-srcware at vinc17 dot net
2014-06-13  9:20 ` fweimer at redhat dot com
2014-08-27 12:59 ` ncoghlan at gmail dot com
2015-08-27 22:20 ` [Bug locale/16621] " jsm28 at gcc dot gnu.org
2015-08-29 20:41 ` vapier at gentoo dot org
2015-08-30  5:59 ` vapier at gentoo dot org [this message]
2015-08-30  6:20 ` ncoghlan at gmail dot com
2021-12-16 21:31 ` carlos at redhat dot com
2022-08-02 10:36 ` nl6720 at gmail dot com
2022-08-02 11:38 ` vincent-srcware at vinc17 dot net
2022-08-02 11:39 ` vincent-srcware at vinc17 dot net
2022-08-02 13:40 ` fweimer at redhat dot com
2022-08-02 14:17 ` vincent-srcware at vinc17 dot net
2022-08-02 14:30 ` fweimer at redhat dot com
2022-08-02 15:15 ` vincent-srcware at vinc17 dot net
2022-08-04 20:46 ` jwilk at jwilk dot net
2022-11-14 13:01 ` fweimer at redhat dot com
2023-09-04 13:29 ` fweimer at redhat dot com
2023-09-04 13:32 ` fweimer at redhat dot com
2023-11-20 15:03 ` cvs-commit at gcc dot gnu.org

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=bug-16621-131-391CMJXQpR@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).