public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vincent-srcware at vinc17 dot net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/16621] C.UTF-8 locales should be regarded like C w.r.t. $LANGUAGE precedence Date: Fri, 21 Feb 2014 13:41:00 -0000 [thread overview] Message-ID: <bug-16621-131-cCZwultNab@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 #2 from Vincent Lefèvre <vincent-srcware at vinc17 dot net> --- (In reply to Andreas Schwab from comment #1) > There is no C.UTF-8 locale in glibc. That's strange, because in the Subversion mailing-list, it was regarded as standard. Subversion works well only in UTF-8 locales, and the suggested solution was to use C.UTF-8: http://mail-archives.apache.org/mod_mbox/subversion-users/201307.mbox/%3C51DC54AD.7010601@wandisco.com%3E -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-21728-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri Feb 21 13:45:26 2014 Return-Path: <glibc-bugs-return-21728-listarch-glibc-bugs=sources.redhat.com@sourceware.org> Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 28239 invoked by alias); 21 Feb 2014 13:45:25 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: <glibc-bugs.sourceware.org> List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org> List-Post: <mailto:glibc-bugs@sourceware.org> List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs> Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 28183 invoked by uid 48); 21 Feb 2014 13:45:20 -0000 From: "y.gribov at samsung dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug math/16600] Glibc floating-point tests fail on VFPv4 platforms Date: Fri, 21 Feb 2014 13:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: 2.21 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: y.gribov at samsung dot com X-Bugzilla-Status: WAITING X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-16600-131-oQVOGp58UY@http.sourceware.org/bugzilla/> In-Reply-To: <bug-16600-131@http.sourceware.org/bugzilla/> References: <bug-16600-131@http.sourceware.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-02/txt/msg00705.txt.bz2 Content-length: 475 https://sourceware.org/bugzilla/show_bug.cgi?id\x16600 --- Comment #3 from Yury Gribov <y.gribov at samsung dot com> --- Sorry for delay, I've sent the email (https://sourceware.org/ml/libc-alpha/2014-02/msg00605.html). A couple of questions: 1) As for regular regeneration: should I look for announcements on some glibc mailing lists? 2) As for this bug: are VFPv4 errors that I see expected? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-02-21 13:41 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 ` vincent-srcware at vinc17 dot net [this message] 2014-06-13 9:20 ` [Bug libc/16621] " 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 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-cCZwultNab@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: linkBe 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).