From: Phillip Wood <phillip.wood123@gmail.com>
To: Brian Lyles <brianmlyles@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH v3] interpret-trailers: handle message without trailing newline
Date: Mon, 9 Sep 2024 10:13:31 +0100 [thread overview]
Message-ID: <ca753ef4-c567-44c3-b4c3-8e483a9a3a95@gmail.com> (raw)
In-Reply-To: <20240906145743.2059405-1-brianmlyles@gmail.com>
Hi Brian
This version looks good to me
Thanks
Phillip
On 06/09/2024 15:50, Brian Lyles wrote:
> When git-interpret-trailers is used to add a trailer to a message that
> does not end in a trailing newline, the new trailer is added on the line
> immediately following the message instead of as a trailer block
> separated from the message by a blank line.
>
> For example, if a message's text was exactly "The subject" with no
> trailing newline present, `git interpret-trailers --trailer
> my-trailer=true` will result in the following malformed commit message:
>
> The subject
> my-trailer: true
>
> While it is generally expected that a commit message should end with a
> newline character, git-interpret-trailers should not be returning an
> invalid message in this case.
>
> Use `strbuf_complete_line` to ensure that the message ends with a
> newline character when reading the input.
>
> Signed-off-by: Brian Lyles <brianmlyles@gmail.com>
> ---
>
> Differences from v2:
> - We now use `strbuf_complete_line` when reading the input file instead
> of handling the lack of a newline when constructing the output, which
> drastically simplifies the patch. Thanks to Phillip for this
> suggestion.
> - Removed some unnecessary `\` in the new tests.
>
> The range-diff from v2 is not included since the patch is so different
> that range-diff is not able to provide anything meaningful.
>
>
> builtin/interpret-trailers.c | 1 +
> t/t7513-interpret-trailers.sh | 40 +++++++++++++++++++++++++++++++++++
> 2 files changed, 41 insertions(+)
>
> diff --git a/builtin/interpret-trailers.c b/builtin/interpret-trailers.c
> index 1d969494cf..e6f22459f1 100644
> --- a/builtin/interpret-trailers.c
> +++ b/builtin/interpret-trailers.c
> @@ -132,6 +132,7 @@ static void read_input_file(struct strbuf *sb, const char *file)
> if (strbuf_read(sb, fileno(stdin), 0) < 0)
> die_errno(_("could not read from stdin"));
> }
> + strbuf_complete_line(sb);
> }
>
> static void interpret_trailers(const struct process_trailer_options *opts,
> diff --git a/t/t7513-interpret-trailers.sh b/t/t7513-interpret-trailers.sh
> index 3d3e13ccf8..d78cae3e04 100755
> --- a/t/t7513-interpret-trailers.sh
> +++ b/t/t7513-interpret-trailers.sh
> @@ -175,6 +175,46 @@ test_expect_success 'with only a title in the message' '
> test_cmp expected actual
> '
>
> +test_expect_success 'with a bodiless message that lacks a trailing newline after the subject' '
> + cat >expected <<-\EOF &&
> + area: change
> +
> + Reviewed-by: Peff
> + Acked-by: Johan
> + EOF
> + printf "area: change" |
> + git interpret-trailers --trailer "Reviewed-by: Peff" \
> + --trailer "Acked-by: Johan" >actual &&
> + test_cmp expected actual
> +'
> +
> +test_expect_success 'with a bodied message that lacks a trailing newline after the body' '
> + cat >expected <<-\EOF &&
> + area: change
> +
> + details about the change.
> +
> + Reviewed-by: Peff
> + Acked-by: Johan
> + EOF
> + printf "area: change\n\ndetails about the change." |
> + git interpret-trailers --trailer "Reviewed-by: Peff" \
> + --trailer "Acked-by: Johan" >actual &&
> + test_cmp expected actual
> +'
> +
> +test_expect_success 'with a message that lacks a trailing newline after the trailers' '
> + cat >expected <<-\EOF &&
> + area: change
> +
> + Reviewed-by: Peff
> + Acked-by: Johan
> + EOF
> + printf "area: change\n\nReviewed-by: Peff" |
> + git interpret-trailers --trailer "Acked-by: Johan" >actual &&
> + test_cmp expected actual
> +'
> +
> test_expect_success 'with multiline title in the message' '
> cat >expected <<-\EOF &&
> place of
> --
> 2.45.2
>
prev parent reply other threads:[~2024-09-09 9:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 17:34 [PATCH] interpret-trailers: handle message without trailing newline Brian Lyles
2024-09-05 18:24 ` Brian Lyles
2024-09-06 4:08 ` [PATCH v2] " Brian Lyles
2024-09-06 9:07 ` Phillip Wood
2024-09-06 15:23 ` Junio C Hamano
2024-09-06 14:50 ` [PATCH v3] " Brian Lyles
2024-09-06 16:21 ` Junio C Hamano
2024-09-09 9:13 ` Phillip Wood
2024-09-09 15:58 ` Junio C Hamano
2024-09-09 9:13 ` Phillip Wood [this message]
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=ca753ef4-c567-44c3-b4c3-8e483a9a3a95@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=brianmlyles@gmail.com \
--cc=git@vger.kernel.org \
--cc=phillip.wood@dunelm.org.uk \
/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).