From: Shlok Kulshreshtha <diy2903@gmail.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 2/2] t: use commit_body to extract commit message bodies
Date: Thu, 30 Jul 2026 23:32:07 +0530 [thread overview]
Message-ID: <20260730180207.83197-1-diy2903@gmail.com> (raw)
In-Reply-To: <xmqqpl05o5n7.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> writes:
> I would not claim to have checked all of these changes, but I did
> spot check a handful and they all looked reasonable.
>
> Shall we mark the topic for 'next'?
Yes, please.
To save you reading all 66 hunks: 63 of them are the same local swap,
where the rev and the output file are unchanged and only the spelling
differs.
-git cat-file commit HEAD | sed -e "1,/^\$/d" >actual
+commit_body HEAD >actual
Each one can be confirmed by looking at the hunk alone.
The three hunks that are worth actual attention are:
* t7509-commit-authorship.sh, the hunk at author_header(). This one
deletes the file's local message_body() helper rather than
substituting anything; its call sites become commit_body elsewhere in
the file.
* t7600-merge.sh, "merge --no-ff --edit". The test grepped the raw
commit object for a phrase and then stripped the header for the
comparison. The phrase is in the body rather than the header, so the
grep now runs against the already-stripped body and both steps share
one commit_body call.
* t3900-i18n-commit.sh, in test_commit_autosquash_multi_encoding().
The stripped body was piped into "iconv". Piping commit_body into
"iconv" would reintroduce the exit-code hole,
so the body is written to a file and "iconv"
reads the file.
Everything else in the patch is the swap above.
next prev parent reply other threads:[~2026-07-30 18:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 22:48 [PATCH 0/2] t: add and use a commit_body test helper Shlok Kulshreshtha
2026-07-26 22:48 ` [PATCH 1/2] test-lib-functions: add commit_body helper Shlok Kulshreshtha
2026-07-26 22:48 ` [PATCH 2/2] t: use commit_body to extract commit message bodies Shlok Kulshreshtha
2026-07-27 8:15 ` [PATCH 0/2] t: add and use a commit_body test helper Junio C Hamano
2026-07-27 9:28 ` Shlok Kulshreshtha
2026-07-27 9:56 ` [PATCH v2 " Shlok Kulshreshtha
2026-07-27 9:56 ` [PATCH v2 1/2] test-lib-functions: add commit_body helper Shlok Kulshreshtha
2026-07-27 9:56 ` [PATCH v2 2/2] t: use commit_body to extract commit message bodies Shlok Kulshreshtha
2026-07-29 21:19 ` Junio C Hamano
2026-07-30 18:02 ` Shlok Kulshreshtha [this message]
2026-07-30 19:38 ` 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=20260730180207.83197-1-diy2903@gmail.com \
--to=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