public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "eblake at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/12045] regex range semantics outside of POSIX should be documented and consistent
Date: Tue, 21 Sep 2010 15:26:00 -0000 [thread overview]
Message-ID: <20100921152630.16526.qmail@sourceware.org> (raw)
In-Reply-To: <20100921152445.12045.eblake@redhat.com>
------- Additional Comments From eblake at redhat dot com 2010-09-21 15:26 -------
Possibly related to the resolution of
http://sources.redhat.com/bugzilla/show_bug.cgi?id=10290
--
http://sourceware.org/bugzilla/show_bug.cgi?id=12045
------- 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:[~2010-09-21 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 15:25 [Bug regex/12045] New: " eblake at redhat dot com
2010-09-21 15:26 ` eblake at redhat dot com [this message]
2010-09-21 15:49 ` [Bug regex/12045] " bonzini at gnu dot org
2010-09-21 22:18 ` eblake at redhat dot com
2010-09-24 12:35 ` [Bug manual/12045] regex range semantics outside of POSIX should be documented bonzini at gnu 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=20100921152630.16526.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--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: 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).