public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tschwinge at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug hurd/11638] regex.c fails to compile on Hurd Date: Fri, 17 Feb 2012 09:22:00 -0000 [thread overview] Message-ID: <bug-11638-131-Z8eyNLNoja@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-11638-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=11638 Thomas Schwinge <tschwinge at sourceware dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tschwinge at sourceware dot | |org --- Comment #4 from Thomas Schwinge <tschwinge at sourceware dot org> 2012-02-17 09:22:28 UTC --- This had just come up on libc-alpha again: <http://sourceware.org/ml/libc-alpha/2012-02/msg00324.html>. I hadn't realized these are imported/shared files. (Shouldn't this be mentioned somewhere prominently?) In this case, we'd go with the upstream fix, obviously. But -- Paul, please have another look at your MIN definition... ;-P -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2012-02-17 9:22 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-11638-131@http.sourceware.org/bugzilla/> 2012-02-17 8:16 ` eggert at gnu dot org 2012-02-17 8:17 ` eggert at gnu dot org 2012-02-17 9:22 ` tschwinge at sourceware dot org [this message] 2012-02-17 13:09 ` joseph at codesourcery dot com 2012-02-20 21:18 ` eggert at gnu dot org 2012-02-20 21:22 ` eggert at gnu dot org 2012-11-04 14:40 ` tschwinge at sourceware dot org 2014-06-30 17:55 ` fweimer at redhat dot com 2010-05-26 14:38 [Bug hurd/11638] New: " aurelien at aurel32 dot net 2010-05-26 14:39 ` [Bug hurd/11638] " aurelien at aurel32 dot net
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-11638-131-Z8eyNLNoja@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.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: 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).