public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "jakub at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/3957] regcomp with REG_NEWLINE flag does operate as POSIX specification for a non-matching list
Date: Mon, 05 Feb 2007 13:43:00 -0000	[thread overview]
Message-ID: <20070205134249.32072.qmail@sourceware.org> (raw)
In-Reply-To: <20070202132302.3957.andrew.mackey@baesystems.com>


------- Additional Comments From jakub at redhat dot com  2007-02-05 13:42 -------
Testing a fix.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|drepper at redhat dot com   |jakub at redhat dot com
             Status|NEW                         |ASSIGNED
            Summary|regcomp with REG_NEWLINE    |regcomp with REG_NEWLINE
                   |flag does operate as POSIX  |flag does operate as POSIX
                   |specification for a non-    |specification for a non-
                   |matching list               |matching list


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

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


  reply	other threads:[~2007-02-05 13:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-02 13:23 [Bug regex/3957] New: " andrew dot mackey at baesystems dot com
2007-02-05 13:43 ` jakub at redhat dot com [this message]
2007-02-05 15:24 ` [Bug regex/3957] " drepper at redhat dot com
2007-07-12 14:50 ` cvs-commit at gcc dot gnu dot org
     [not found] <bug-3957-132@http.sourceware.org/bugzilla/>
2014-02-16 17:44 ` jackie.rosen at hushmail dot com
2014-05-28 19:41 ` 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=20070205134249.32072.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).