This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug locale/20974] bs_BA: yesexpr/noexpr regexes accept any character
- From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Fri, 30 Dec 2016 06:51:51 +0000
- Subject: [Bug locale/20974] bs_BA: yesexpr/noexpr regexes accept any character
- Auto-submitted: auto-generated
- References: <bug-20974-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20974
--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".
The branch, release/2.24/master has been updated
via 7e4405c50fc374d5e80141554c7887a52d1f9118 (commit)
from e9e69e468039fcd57276f783a16aa771a8e4214e (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=7e4405c50fc374d5e80141554c7887a52d1f9118
commit 7e4405c50fc374d5e80141554c7887a52d1f9118
Author: Mike Frysinger <vapier@gentoo.org>
Date: Thu Dec 15 18:34:05 2016 -0500
localedata: bs_BA: fix yesexpr/noexpr [BZ #20974]
Both regexes end with a "*." which means the previous match can be
omitted, and then the . allows them to match any input at all.
This means tools like coreutils' `rm -i` will always delete things
when prompted because the yesexpr regex matches all inputs (even
the negative ones).
(cherry picked from commit a035eb6928bc63fb798dcc1421529f933122d74f)
-----------------------------------------------------------------------
Summary of changes:
localedata/ChangeLog | 6 ++++++
localedata/locales/bs_BA | 4 ++--
2 files changed, 8 insertions(+), 2 deletions(-)
--
You are receiving this mail because:
You are on the CC list for the bug.