public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Paul Eggert <eggert@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] Fix BRE typos in check-safety.sh Date: Wed, 14 Sep 2022 05:12:26 +0000 (GMT) [thread overview] Message-ID: <20220914051226.9E17C389839F@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=05967faf0e3df6aad07f0b05e138e86f82363deb commit 05967faf0e3df6aad07f0b05e138e86f82363deb Author: Paul Eggert <eggert@cs.ucla.edu> Date: Wed Sep 14 00:10:45 2022 -0500 Fix BRE typos in check-safety.sh * manual/check-safety.sh: Fix BRE portability typos. POSIX says \] produces undefined results. Diff: --- manual/check-safety.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/manual/check-safety.sh b/manual/check-safety.sh index 21ddb3beb7..25f9fb5b11 100644 --- a/manual/check-safety.sh +++ b/manual/check-safety.sh @@ -109,15 +109,15 @@ success=false # optional comment about exclusions is between []s at the end of the # line. grep -n '^@c \+[^@ ]\+\( dup\)\?'\ -'\( @\(mt\|a[sc]\)[^ ]*\)*\( \[.*\]\)\?$' "$@" | +'\( @\(mt\|a[sc]\)[^ ]*\)*\( \[.*]\)\?$' "$@" | grep -v ':@c *[^@{}]*\( @mt[^ {}]*\)*'\ -'\( @as[^ {}]*\)*\( @ac[^ {}]*\)*\( \[.*\]\)\?$' && +'\( @as[^ {}]*\)*\( @ac[^ {}]*\)*\( \[.*]\)\?$' && success=false # Check that comments containing safety remarks do not contain # duplicate remarks. grep -n '^@c \+[^@ ]\+\( dup\)\?'\ -'\( @\(mt\|a[sc]\)[^ ]*\)*\( \[.*\]\)\?$' "$@" | +'\( @\(mt\|a[sc]\)[^ ]*\)*\( \[.*]\)\?$' "$@" | grep '[^:]\(@\(mt\|a[sc]\)[^ ]*\) \(.*[^:]\)\?\1\($\| \)' && success=false
reply other threads:[~2022-09-14 5:12 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220914051226.9E17C389839F@sourceware.org \ --to=eggert@sourceware.org \ --cc=glibc-cvs@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: 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).