public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aj at suse dot de" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug build/10535] mis-installation of code during check sequence glibc 2.10.1 Date: Sat, 01 Dec 2012 16:41:00 -0000 [thread overview] Message-ID: <bug-10535-131-5nIfLO75i8@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-10535-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=10535 Andreas Jaeger <aj at suse dot de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution| |INVALID --- Comment #3 from Andreas Jaeger <aj at suse dot de> 2012-12-01 16:41:25 UTC --- Thomas, please open a separate bug for what you describe if that issue is still open. I'm marking this now as invalid, since there's no reaction to my question for answers. -- 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-12-01 16:41 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-10535-131@http.sourceware.org/bugzilla/> 2011-07-03 12:44 ` [Bug admin/10535] " aj at suse dot de 2012-02-07 18:59 ` [Bug libc/10535] " carlos at systemhalted dot org 2012-02-07 19:01 ` carlos at systemhalted dot org 2012-02-08 19:48 ` tschwinge at sourceware dot org 2012-02-21 2:05 ` [Bug build/10535] " jsm28 at gcc dot gnu.org 2012-12-01 16:41 ` aj at suse dot de [this message] 2014-07-01 7:04 ` fweimer at redhat dot com
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-10535-131-5nIfLO75i8@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).