From: Patrick Steinhardt <ps@pks.im>
To: Shlok Kulshreshtha <diy2903@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 1/2] t1100: modernize test style
Date: Tue, 14 Jul 2026 09:39:33 +0200 [thread overview]
Message-ID: <alXntdc-FO-1IHSV@pks.im> (raw)
In-Reply-To: <20260713140142.27898-2-diy2903@gmail.com>
On Mon, Jul 13, 2026 at 07:31:40PM +0530, Shlok Kulshreshtha wrote:
> diff --git a/t/t1100-commit-tree-options.sh b/t/t1100-commit-tree-options.sh
> index ae66ba5bab..fabe5a97cb 100755
> --- a/t/t1100-commit-tree-options.sh
> +++ b/t/t1100-commit-tree-options.sh
> @@ -22,28 +22,28 @@ committer Committer Name <committer@email> 1117150200 +0000
> comment text
> EOF
>
> -test_expect_success \
> - 'test preparation: write empty tree' \
> - 'git write-tree >treeid'
> -
> -test_expect_success \
> - 'construct commit' \
> - 'echo comment text |
> - GIT_AUTHOR_NAME="Author Name" \
> - GIT_AUTHOR_EMAIL="author@email" \
> - GIT_AUTHOR_DATE="2005-05-26 23:00" \
> - GIT_COMMITTER_NAME="Committer Name" \
> - GIT_COMMITTER_EMAIL="committer@email" \
> - GIT_COMMITTER_DATE="2005-05-26 23:30" \
> - TZ=GMT git commit-tree $(cat treeid) >commitid 2>/dev/null'
> -
> -test_expect_success \
> - 'read commit' \
> - 'git cat-file commit $(cat commitid) >commit'
> -
> -test_expect_success \
> - 'compare commit' \
> - 'test_cmp expected commit'
> +test_expect_success 'test preparation: write empty tree' '
> + git write-tree >treeid
> +'
> +
> +test_expect_success 'construct commit' '
> + echo comment text |
> + GIT_AUTHOR_NAME="Author Name" \
> + GIT_AUTHOR_EMAIL="author@email" \
> + GIT_AUTHOR_DATE="2005-05-26 23:00" \
> + GIT_COMMITTER_NAME="Committer Name" \
> + GIT_COMMITTER_EMAIL="committer@email" \
> + GIT_COMMITTER_DATE="2005-05-26 23:30" \
> + TZ=GMT git commit-tree $(cat treeid) >commitid 2>/dev/null
> +'
> +
> +test_expect_success 'read commit' '
> + git cat-file commit $(cat commitid) >commit
> +'
> +
> +test_expect_success 'compare commit' '
> + test_cmp expected commit
> +'
>
>
> test_expect_success 'flags and then non flags' '
Nit: let's remove the extraneous empty line while at it.
Patrick
next prev parent reply other threads:[~2026-07-14 7:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 14:01 [PATCH 0/2] t1100: modernize test script Shlok Kulshreshtha
2026-07-13 14:01 ` [PATCH 1/2] t1100: modernize test style Shlok Kulshreshtha
2026-07-13 16:30 ` Junio C Hamano
2026-07-14 7:39 ` Patrick Steinhardt [this message]
2026-07-13 14:01 ` [PATCH 2/2] t1100: move creation of expected output into setup test Shlok Kulshreshtha
2026-07-13 16:10 ` Junio C Hamano
2026-07-14 7:16 ` [PATCH v2 0/2] t1100: modernize test script Shlok Kulshreshtha
2026-07-14 7:16 ` [PATCH v2 1/2] t1100: modernize test style Shlok Kulshreshtha
2026-07-14 7:16 ` [PATCH v2 2/2] t1100: move creation of expected output into setup test Shlok Kulshreshtha
2026-07-14 12:20 ` [PATCH v3 0/2] t1100: modernize test script Shlok Kulshreshtha
2026-07-14 12:20 ` [PATCH v3 1/2] t1100: modernize test style Shlok Kulshreshtha
2026-07-14 12:20 ` [PATCH v3 2/2] t1100: move creation of expected output into setup test Shlok Kulshreshtha
2026-07-14 13:56 ` [PATCH v3 0/2] t1100: modernize test script Patrick Steinhardt
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=alXntdc-FO-1IHSV@pks.im \
--to=ps@pks.im \
--cc=diy2903@gmail.com \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox