public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "eggert at cs dot ucla.edu" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sourceware.org
Subject: [Bug regex/11053] Wrong results with backreferences
Date: Wed, 07 Sep 2022 04:31:20 +0000 [thread overview]
Message-ID: <bug-11053-132-Nno0IM4cXA@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11053-132@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=11053
--- Comment #22 from eggert at cs dot ucla.edu ---
(In reply to Vincent Lefèvre from comment #21)
> (In reply to eggert from comment #20)
> > OK, so in that case how about if we update Bug#17356 by (1) saying it is no
> > longer a duplicate of Bug#11053 (as we've fixed the latter but not the
> > former), and (2) reopening Bug#17536? If I understand you correctly, that
> > would match the symptoms you describe.
>
> Yes, I think that this is the best solution.
OK, done.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-09-07 4:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11053-132@http.sourceware.org/bugzilla/>
2014-06-30 20:34 ` fweimer at redhat dot com
2014-06-30 20:34 ` fweimer at redhat dot com
2014-09-23 2:28 ` eggert at gnu dot org
2014-09-23 7:55 ` fweimer at redhat dot com
2017-01-17 21:24 ` eggert at gnu dot org
2021-02-06 7:37 ` eggert at cs dot ucla.edu
2021-03-04 7:33 ` mliska at suse dot cz
2021-08-16 0:55 ` sam at gentoo dot org
2021-08-16 7:08 ` simon_a_taylor at yahoo dot com
2021-08-25 5:10 ` michael.hudson at canonical dot com
2021-08-25 18:09 ` eggert at cs dot ucla.edu
2021-09-21 15:00 ` cvs-commit at gcc dot gnu.org
2022-09-05 23:06 ` vincent-srcware at vinc17 dot net
2022-09-06 0:37 ` eggert at cs dot ucla.edu
2022-09-06 2:47 ` vincent-srcware at vinc17 dot net
2022-09-06 2:59 ` vincent-srcware at vinc17 dot net
2022-09-06 18:47 ` eggert at cs dot ucla.edu
2022-09-06 22:56 ` vincent-srcware at vinc17 dot net
2022-09-06 23:41 ` eggert at cs dot ucla.edu
2022-09-07 0:17 ` vincent-srcware at vinc17 dot net
2022-09-07 4:31 ` eggert at cs dot ucla.edu [this message]
2022-09-07 10:31 ` vincent-srcware at vinc17 dot net
2022-09-07 20:57 ` eggert at cs dot ucla.edu
2022-09-08 11:44 ` vincent-srcware at vinc17 dot net
2022-11-11 16:29 ` cvs-commit at gcc dot gnu.org
2009-12-04 19:36 [Bug regex/11053] New: Segfault on invalid backreference bonzini at gnu dot org
2010-04-09 17:46 ` [Bug regex/11053] Wrong results with backreferences 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=bug-11053-132-Nno0IM4cXA@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs-regex@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: 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).