public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "drepper at redhat dot com" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs-regex@sources.redhat.com Subject: [Bug regex/500] regex code can be optimized a lot Date: Thu, 27 Jan 2005 19:08:00 -0000 [thread overview] Message-ID: <20050127190834.24672.qmail@sourceware.org> (raw) In-Reply-To: <20041104084631.500.bonzini@gnu.org> ------- Additional Comments From drepper at redhat dot com 2005-01-27 19:08 ------- All dependencies handled. -- What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED http://sources.redhat.com/bugzilla/show_bug.cgi?id=500 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2005-01-27 19:08 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-11-04 8:46 [Bug regex/500] New: " bonzini at gnu dot org 2004-11-04 8:51 ` [Bug regex/500] " bonzini at gnu dot org 2004-11-04 8:54 ` bonzini at gnu dot org 2004-11-04 8:55 ` bonzini at gnu dot org 2004-11-04 8:56 ` bonzini at gnu dot org 2004-11-04 8:59 ` bonzini at gnu dot org 2004-11-04 9:00 ` bonzini at gnu dot org 2004-11-04 9:04 ` bonzini at gnu dot org 2004-11-09 7:49 ` bonzini at gnu dot org 2004-11-09 7:55 ` bonzini at gnu dot org 2004-11-09 7:55 ` bonzini at gnu dot org 2004-11-10 14:30 ` drepper at redhat dot com 2004-11-10 15:47 ` drepper at redhat dot com 2004-11-10 18:50 ` drepper at redhat dot com 2004-11-23 12:31 ` bonzini at gnu dot org 2004-12-10 16:54 ` bonzini at gnu dot org 2004-12-27 16:41 ` drepper at redhat dot com 2005-01-26 22:28 ` drepper at redhat dot com 2005-01-27 19:08 ` drepper at redhat dot com [this message] 2005-01-27 19:08 ` drepper 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=20050127190834.24672.qmail@sourceware.org \ --to=sourceware-bugzilla@sources.redhat.com \ --cc=glibc-bugs-regex@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).