From: Derrick Stolee <stolee@gmail.com>
To: Kevin Lyles via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Cc: Kevin Lyles <klyles+github@epic.com>
Subject: Re: [PATCH v2 2/2] Mark 'git cat-file' sparse-index compatible
Date: Tue, 3 Sep 2024 10:17:14 -0400 [thread overview]
Message-ID: <83ec9352-d274-4d05-a6b8-d33924f46205@gmail.com> (raw)
In-Reply-To: <a92825e502f1795910b869165779279b89212939.1725052243.git.gitgitgadget@gmail.com>
On 8/30/24 5:10 PM, Kevin Lyles via GitGitGadget wrote:
> From: Kevin Lyles <klyles+github@epic.com>
> +test_expect_success 'cat-file -p' '
> + init_repos &&
> + echo "new content" >>full-checkout/deep/a &&
> + echo "new content" >>sparse-checkout/deep/a &&
> + echo "new content" >>sparse-index/deep/a &&
> + run_on_all git add deep/a &&
> +
> + test_all_match git cat-file -p :deep/a &&
> + ensure_not_expanded cat-file -p :deep/a &&
> + test_all_match git cat-file -p :folder1/a &&
> + ensure_expanded cat-file -p :folder1/a'
There's one style issue that I missed in the previous version,
which is that the final single-quote (') should be on a new line
after the last line of the test. like this:
---
test_all_match git cat-file -p :folder1/a &&
ensure_expanded cat-file -p :folder1/a
'
---
> +test_expect_success 'cat-file --batch' '
> + init_repos &&
> + echo "new content" >>full-checkout/deep/a &&
> + echo "new content" >>sparse-checkout/deep/a &&
> + echo "new content" >>sparse-index/deep/a &&
> + run_on_all git add deep/a &&
> +
> + echo ":deep/a">in &&
> + test_all_match git cat-file --batch <in &&
> + ensure_not_expanded cat-file --batch <in &&
> +
> + echo ":folder1/a">in &&
> + test_all_match git cat-file --batch <in &&
> + ensure_expanded cat-file --batch <in &&
> +
> + cat <<-\EOF >in &&
nit: typically we would write this as "cat >in <<-\EOF &&"
> + :deep/a
> + :folder1/a
> + EOF
> + test_all_match git cat-file --batch <in &&
> + ensure_expanded cat-file --batch <in'
> +
Pointing out the final single-quote here, too.
Thank you for updating the heredocs and other format things that
I noticed in the previous version. Also, thanks for splitting the
patch into two parts.
Thanks for working on this!
-Stolee
next prev parent reply other threads:[~2024-09-03 14:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 18:08 [PATCH] Mark `cat-file` sparse-index compatible Kevin Lyles via GitGitGadget
2024-08-29 1:59 ` Derrick Stolee
2024-08-30 21:10 ` [PATCH v2 0/2] Mark cat-file " Kevin Lyles via GitGitGadget
2024-08-30 21:10 ` [PATCH v2 1/2] Allow using stdin in run_on_* functions Kevin Lyles via GitGitGadget
2024-08-30 21:10 ` [PATCH v2 2/2] Mark 'git cat-file' sparse-index compatible Kevin Lyles via GitGitGadget
2024-09-03 14:17 ` Derrick Stolee [this message]
2024-09-03 17:21 ` Junio C Hamano
2024-09-03 17:54 ` [PATCH v3 0/2] " Kevin Lyles via GitGitGadget
2024-09-03 17:54 ` [PATCH v3 1/2] Allow using stdin in run_on_* functions Kevin Lyles via GitGitGadget
2024-09-03 19:11 ` Junio C Hamano
2024-09-03 17:54 ` [PATCH v3 2/2] Mark 'git cat-file' sparse-index compatible Kevin Lyles via GitGitGadget
2024-09-03 19:19 ` Junio C Hamano
2024-09-03 22:06 ` [PATCH v4 0/2] builtin/cat-file: mark " Kevin Lyles via GitGitGadget
2024-09-03 22:06 ` [PATCH v4 1/2] t1092: allow run_on_* functions to use standard input Kevin Lyles via GitGitGadget
2024-09-04 16:23 ` Junio C Hamano
2024-09-03 22:06 ` [PATCH v4 2/2] builtin/cat-file: mark 'git cat-file' sparse-index compatible Kevin Lyles via GitGitGadget
2024-09-04 16:35 ` Junio C Hamano
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=83ec9352-d274-4d05-a6b8-d33924f46205@gmail.com \
--to=stolee@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=klyles+github@epic.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;
as well as URLs for NNTP newsgroup(s).