From: Danh Doan <congdanhqx@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH v2 1/6] t4061: use POSIX compliance regex(7)
Date: Sun, 22 Mar 2020 08:52:33 +0700 [thread overview]
Message-ID: <20200322015233.GB11801@danh.dev> (raw)
In-Reply-To: <4830bd3aaf6cadc02c00732f8447646064a6ae3e.1584838133.git.congdanhqx@gmail.com>
On 2020-03-22 07:55:10+0700, Đoàn Trần Công Danh <congdanhqx@gmail.com> wrote:
> BRE interprets `+` literally, and
> `\+` is undefined for POSIX BRE, from:
> https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html#tag_09_03_02
>
> > The interpretation of an ordinary character preceded
> > by an unescaped <backslash> ( '\\' ) is undefined, except for:
> > - The characters ')', '(', '{', and '}'
> > - The digits 1 to 9 inclusive
> > - A character inside a bracket expression
>
> This test is failing with busybox sed, the default sed of Alpine Linux
>
> Fix it by using literal `+` instead.
>
> Signed-off-by: Đoàn Trần Công Danh <congdanhqx@gmail.com>
Due to error in my part, please ignore the v2 with 6 patches.
It's the same with v1.
Please look into v2 with 8 patches instead.
Sorry for the noise.
--
Danh
next prev parent reply other threads:[~2020-03-22 1:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1584838133.git.congdanhqx@gmail.com>
2020-03-22 0:55 ` [PATCH v2 1/6] t4061: use POSIX compliance regex(7) Đoàn Trần Công Danh
2020-03-22 1:52 ` Danh Doan [this message]
2020-03-22 0:55 ` [PATCH v2 3/6] t5003: skip conversion test if unzip -a is unavailable Đoàn Trần Công Danh
2020-03-22 0:55 ` [PATCH v2 4/6] t5616: use rev-parse instead to get HEAD's object_id Đoàn Trần Công Danh
2020-03-22 0:55 ` [PATCH v2 5/6] t7063: use POSIX find(1) syntax Đoàn Trần Công Danh
2020-03-22 0:55 ` [PATCH v2 6/6] t4124: fix test for non-compliance diff Đoàn Trần Công Danh
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=20200322015233.GB11801@danh.dev \
--to=congdanhqx@gmail.com \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.