public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "bonzini at gnu dot org" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs-regex@sources.redhat.com Subject: [Bug regex/503] fastmap loop in regex can be tightened Date: Wed, 10 Nov 2004 11:03:00 -0000 [thread overview] Message-ID: <20041110110308.19276.qmail@sourceware.org> (raw) In-Reply-To: <20041104085545.503.bonzini@gnu.org> ------- Additional Comments From bonzini at gnu dot org 2004-11-10 11:03 ------- Created an attachment (id=277) --> (http://sources.redhat.com/bugzilla/attachment.cgi?id=277&action=view) updated patch, fixed ChangeLog entry -- What |Removed |Added ---------------------------------------------------------------------------- Attachment #275 is|0 |1 obsolete| | http://sources.redhat.com/bugzilla/show_bug.cgi?id=503 ------- 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:[~2004-11-10 11:03 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-11-04 8:55 [Bug regex/503] New: " bonzini at gnu dot org 2004-11-10 10:56 ` [Bug regex/503] " bonzini at gnu dot org 2004-11-10 11:03 ` bonzini at gnu dot org [this message] 2004-11-10 15:47 ` 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=20041110110308.19276.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).