public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/2672] going libc_pic.a to libc_pic.os discard gets into the way
Date: Thu, 10 Aug 2006 06:17:00 -0000	[thread overview]
Message-ID: <20060810061701.25188.qmail@sourceware.org> (raw)
In-Reply-To: <20060517180018.2672.malitzke@metronets.com>


------- Additional Comments From pinskia at gcc dot gnu dot org  2006-08-10 06:17 -------
And this is a real glibc bug.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |


http://sourceware.org/bugzilla/show_bug.cgi?id=2672

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2006-08-10  6:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-17 18:00 [Bug libc/2672] New: " malitzke at metronets dot com
2006-05-17 18:04 ` [Bug libc/2672] " malitzke at metronets dot com
2006-05-17 18:42 ` decimal at us dot ibm dot com
2006-08-04  2:39 ` pinskia at gcc dot gnu dot org
2006-08-04  2:39 ` pinskia at gcc dot gnu dot org
2006-08-04 15:22 ` pinskia at gcc dot gnu dot org
2006-08-04 15:22 ` pinskia at gcc dot gnu dot org
2006-08-10  6:17 ` pinskia at gcc dot gnu dot org [this message]
2006-08-10  6:19 ` pinskia at gcc dot gnu dot org
2006-08-24  6:58 ` drepper at redhat dot com
     [not found] <bug-2672-131@http.sourceware.org/bugzilla/>
2014-02-16 19:32 ` jackie.rosen at hushmail dot com
2014-05-28 19:47 ` schwab at sourceware dot org
2014-05-28 19:47 ` schwab at sourceware dot 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=20060810061701.25188.qmail@sourceware.org \
    --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: 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).