public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jackie.rosen at hushmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug build/333] Obsolete bug, report build bugs in "build" component (was: Do not report build errors in bugzilla!) Date: Sun, 16 Feb 2014 17:46:00 -0000 [thread overview] Message-ID: <bug-333-131-MRGlQf01Kl@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-333-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=333 Jackie Rosen <jackie.rosen at hushmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jackie.rosen at hushmail dot com --- Comment #118 from Jackie Rosen <jackie.rosen at hushmail dot com> --- *** Bug 260998 has been marked as a duplicate of this bug. *** Seen from the domain http://volichat.com Page where seen: http://volichat.com/adult-chat-rooms Marked for reference. Resolved as fixed @bugzilla. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-02-16 17:46 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-333-131@http.sourceware.org/bugzilla/> 2011-01-16 16:08 ` [Bug faq/333] Do not report build errors in bugzilla! drepper.fsp at gmail dot com 2011-06-08 23:32 ` drepper.fsp at gmail dot com 2011-07-12 14:34 ` drepper.fsp at gmail dot com 2011-07-20 16:18 ` drepper.fsp at gmail dot com 2011-07-22 1:38 ` drepper.fsp at gmail dot com 2012-02-18 15:08 ` jsm28 at gcc dot gnu.org 2012-02-21 0:10 ` [Bug faq/333] Obsolete bug, report build bugs in "build" component (was: Do not report build errors in bugzilla!) jsm28 at gcc dot gnu.org 2012-02-22 0:32 ` [Bug build/333] " roland at gnu dot org 2014-02-16 17:46 ` jackie.rosen at hushmail dot com [this message] 2014-05-28 19:45 ` schwab at sourceware dot org 2014-06-27 12:53 ` 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-333-131-MRGlQf01Kl@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).