public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "maxim.kuvyrkov at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/14898] Unable to create small static TLS block in shared library Date: Wed, 05 Dec 2012 06:24:00 -0000 [thread overview] Message-ID: <bug-14898-131-oTL1IWOoim@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14898-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14898 Maxim Kuvyrkov <maxim.kuvyrkov at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|2.15.1 |2.18 --- Comment #7 from Maxim Kuvyrkov <maxim.kuvyrkov at gmail dot com> 2012-12-05 06:24:13 UTC --- Andreas, Was your patch posted to libc-alpha@? -- 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-05 6:24 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-30 17:12 [Bug libc/14898] New: " bramesh.dev at gmail dot com 2012-11-30 17:25 ` [Bug libc/14898] " carlos_odonell at mentor dot com 2012-11-30 20:21 ` schwab@linux-m68k.org 2012-12-02 23:05 ` maxim.kuvyrkov at gmail dot com 2012-12-04 0:01 ` carlos at systemhalted dot org 2012-12-04 2:40 ` maxim.kuvyrkov at gmail dot com 2012-12-04 2:47 ` maxim.kuvyrkov at gmail dot com 2012-12-04 3:46 ` bramesh.dev at gmail dot com 2012-12-04 9:23 ` schwab@linux-m68k.org 2012-12-04 22:49 ` bramesh.dev at gmail dot com 2012-12-05 6:24 ` maxim.kuvyrkov at gmail dot com [this message] 2012-12-05 21:40 ` bramesh.dev at gmail dot com 2012-12-05 22:49 ` law at redhat dot com 2013-01-14 14:13 ` schwab@linux-m68k.org 2014-06-14 7:44 ` 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-14898-131-oTL1IWOoim@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).