From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: <git@vger.kernel.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Junio C Hamano <gitster@pobox.com>
Subject: [PATCH v3 17/21] t5607: make hash size independent
Date: Fri, 7 Feb 2020 00:52:50 +0000 [thread overview]
Message-ID: <20200207005254.1495851-18-sandals@crustytoothpaste.net> (raw)
In-Reply-To: <20200207005254.1495851-1-sandals@crustytoothpaste.net>
Use $OID_REGEX instead of a hard-coded regular expression.
Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
---
t/t5607-clone-bundle.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/t/t5607-clone-bundle.sh b/t/t5607-clone-bundle.sh
index b7a3fdf02d..9108ff6fbd 100755
--- a/t/t5607-clone-bundle.sh
+++ b/t/t5607-clone-bundle.sh
@@ -64,7 +64,7 @@ test_expect_success 'ridiculously long subject in boundary' '
test -s heads &&
git fetch long-subject-bundle.bdl &&
sed -n "/^-/{p;q;}" long-subject-bundle.bdl >boundary &&
- grep "^-[0-9a-f]\\{40\\} " boundary
+ grep "^-$OID_REGEX " boundary
'
test_expect_success 'prerequisites with an empty commit message' '
next prev parent reply other threads:[~2020-02-07 0:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 0:52 [PATCH v3 00/21] SHA-256 test fixes, part 8 brian m. carlson
2020-02-07 0:52 ` [PATCH v3 01/21] t/lib-pack: support SHA-256 brian m. carlson
2020-02-07 0:52 ` [PATCH v3 02/21] t3206: make hash size independent brian m. carlson
2020-02-07 0:52 ` [PATCH v3 03/21] t3308: make test work with SHA-256 brian m. carlson
2020-02-07 0:52 ` [PATCH v3 04/21] t3309: " brian m. carlson
2020-02-07 0:52 ` [PATCH v3 05/21] t3310: " brian m. carlson
2020-02-07 0:52 ` [PATCH v3 06/21] t3311: " brian m. carlson
2020-02-07 0:52 ` [PATCH v3 07/21] t4013: make test hash independent brian m. carlson
2020-02-07 0:52 ` [PATCH v3 08/21] t4211: move SHA-1-specific test cases into a directory brian m. carlson
2020-02-07 0:52 ` [PATCH v3 09/21] t4211: add test cases for SHA-256 brian m. carlson
2020-02-07 0:52 ` [PATCH v3 10/21] t4060: make test work with SHA-256 brian m. carlson
2020-02-07 0:52 ` [PATCH v3 11/21] t5302: make hash size independent brian m. carlson
2020-02-07 0:52 ` [PATCH v3 12/21] t5309: make test hash independent brian m. carlson
2020-02-07 0:52 ` [PATCH v3 13/21] t5313: " brian m. carlson
2020-02-07 0:52 ` [PATCH v3 14/21] t5321: " brian m. carlson
2020-02-07 0:52 ` [PATCH v3 15/21] t5515: " brian m. carlson
2020-02-07 0:52 ` [PATCH v3 16/21] t5318: update for SHA-256 brian m. carlson
2020-02-07 0:52 ` brian m. carlson [this message]
2020-02-07 0:52 ` [PATCH v3 18/21] t5703: make test work with SHA-256 brian m. carlson
2020-02-07 0:52 ` [PATCH v3 19/21] t6000: abstract away SHA-1-specific constants brian m. carlson
2020-02-07 0:52 ` [PATCH v3 20/21] t6006: make hash size independent brian m. carlson
2020-02-07 0:52 ` [PATCH v3 21/21] t6024: update for SHA-256 brian m. carlson
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200207005254.1495851-18-sandals@crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).