From: Junio C Hamano <gitster@pobox.com>
To: Marcel Telka <marcel@telka.sk>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Switch grep from non-portable BRE to portable ERE
Date: Fri, 17 May 2024 11:02:28 -0700 [thread overview]
Message-ID: <xmqq7cfsiaff.fsf@gitster.g> (raw)
In-Reply-To: <ZkePejx-eRNrspZ2@telcontar> (Marcel Telka's message of "Fri, 17 May 2024 19:10:18 +0200")
Marcel Telka <marcel@telka.sk> writes:
> Subject: Re: [PATCH] Switch grep from non-portable BRE to portable ERE
>
> This makes the grep usage fully POSIX compliant.
May want to mention that using backslash to invoke ERE feature in
BRE is a GNU extension?
Thanks for this and other portability patches. You are porting to a
new platform, I presume, where either nobody else ported to before
or those who ported did not bother reporting test breakages to us?
> Signed-off-by: Marcel Telka <marcel@telka.sk>
> ---
> mergetools/vimdiff | 2 +-
> t/t1404-update-ref-errors.sh | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/mergetools/vimdiff b/mergetools/vimdiff
> index 734d15a03b..f8ad6b35d4 100644
> --- a/mergetools/vimdiff
> +++ b/mergetools/vimdiff
> @@ -325,7 +325,7 @@ gen_cmd () {
> fi
>
> # If this is a single window diff with all the buffers
> - if ! echo "$tab" | grep ",\|/" >/dev/null
> + if ! echo "$tab" | grep -E ",|/" >/dev/null
> then
> CMD="$CMD | silent execute 'bufdo diffthis'"
> fi
> diff --git a/t/t1404-update-ref-errors.sh b/t/t1404-update-ref-errors.sh
> index 98e9158bd2..67ebd81a4c 100755
> --- a/t/t1404-update-ref-errors.sh
> +++ b/t/t1404-update-ref-errors.sh
> @@ -100,7 +100,7 @@ df_test() {
> printf "%s\n" "delete $delname" "create $addname $D"
> fi >commands &&
> test_must_fail git update-ref --stdin <commands 2>output.err &&
> - grep "fatal:\( cannot lock ref $SQ$addname$SQ:\)\? $SQ$delref$SQ exists; cannot create $SQ$addref$SQ" output.err &&
> + grep -E "fatal:( cannot lock ref $SQ$addname$SQ:)? $SQ$delref$SQ exists; cannot create $SQ$addref$SQ" output.err &&
> printf "%s\n" "$C $delref" >expected-refs &&
> git for-each-ref --format="%(objectname) %(refname)" $prefix/r >actual-refs &&
> test_cmp expected-refs actual-refs
next prev parent reply other threads:[~2024-05-17 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 17:10 [PATCH] Switch grep from non-portable BRE to portable ERE Marcel Telka
2024-05-17 18:02 ` Junio C Hamano [this message]
2024-05-17 18:50 ` Marcel Telka
2024-05-17 19:02 ` Marcel Telka
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=xmqq7cfsiaff.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=marcel@telka.sk \
/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