From: Junio C Hamano <gitster@pobox.com>
To: "Rubén Justo" <rjusto@gmail.com>
Cc: Git List <git@vger.kernel.org>, Patrick Steinhardt <ps@pks.im>
Subject: Re: [PATCH] format-patch: assume --cover-letter for diff in multi-patch series
Date: Wed, 05 Jun 2024 11:17:46 -0700 [thread overview]
Message-ID: <xmqqbk4fs185.fsf@gitster.g> (raw)
In-Reply-To: <14365d68-ed04-44fe-823b-a3959626684e@gmail.com> ("Rubén Justo"'s message of "Wed, 5 Jun 2024 20:01:21 +0200")
Rubén Justo <rjusto@gmail.com> writes:
> diff --git a/builtin/log.c b/builtin/log.c
> index c8ce0c0d88..8032909d4f 100644
> --- a/builtin/log.c
> +++ b/builtin/log.c
> @@ -2277,6 +2277,8 @@ int cmd_format_patch(int argc, const char **argv, const char *prefix)
> if (cover_letter == -1) {
> if (config_cover_letter == COVER_AUTO)
> cover_letter = (total > 1);
> + else if ((idiff_prev.nr || rdiff_prev) && (total > 1))
> + cover_letter = (config_cover_letter != COVER_OFF);
> else
> cover_letter = (config_cover_letter == COVER_ON);
> }
Interesting. So those who really really hate cover letters can set
the configuration explicitly to 'off' and giving an --interdiff
option would still have the sanity check kick in. Makes sense.
> diff --git a/t/t3206-range-diff.sh b/t/t3206-range-diff.sh
> index 7b05bf3961..5af155805d 100755
> --- a/t/t3206-range-diff.sh
> +++ b/t/t3206-range-diff.sh
> @@ -545,6 +545,12 @@ do
> '
> done
>
> +test_expect_success "format-patch --range-diff, implicit --cover-letter" '
> + git format-patch -v2 --range-diff=topic main..unmodified &&
> + test_when_finished "rm v2-000?-*" &&
I was about to make the follwoing:
Swap these two. Arrange things we are going to create to be
removed at end, and then start creating them. That way, we will
clean them up even if we fail after creating some but before the
end of the command.
but this one is littered with exiting breakage, so I'll let it pass.
Somebody will later go in and fix them all (#leftoverbits).
> + test_grep "^Range-diff against v1:$" v2-0000-*
> +'
Isn't the name of the cover letter file always cover-letter.patch
unless you configure a custom --suffix (which is not the case here)?
> diff --git a/t/t4014-format-patch.sh b/t/t4014-format-patch.sh
> index ba85b582c5..c844fbfe47 100755
> --- a/t/t4014-format-patch.sh
> +++ b/t/t4014-format-patch.sh
> @@ -2492,6 +2492,12 @@ test_expect_success 'interdiff: solo-patch' '
> test_cmp expect actual
> '
>
> +test_expect_success 'interdiff: multi-patch, implicit --cover-letter' '
> + git format-patch --interdiff=boop~2 -2 -v23 &&
> + test_grep "^Interdiff against v22:$" v23-0000-cover-letter.patch &&
> + test_cmp expect actual
> +'
OK.
> test_expect_success 'format-patch does not respect diff.noprefix' '
> git -c diff.noprefix format-patch -1 --stdout >actual &&
> grep "^--- a/blorp" actual
Looking good.
next prev parent reply other threads:[~2024-06-05 18:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 22:49 [PATCH] format-patch: assume --cover-letter for diff in multi-patch series Rubén Justo
2024-06-04 8:02 ` Patrick Steinhardt
2024-06-04 17:32 ` Junio C Hamano
2024-06-05 18:01 ` Rubén Justo
2024-06-05 18:17 ` Junio C Hamano [this message]
2024-06-05 18:58 ` Junio C Hamano
2024-06-05 20:27 ` [PATCH v3] " Rubén Justo
2024-06-05 20:44 ` Junio C Hamano
2024-06-05 21:24 ` Rubén Justo
2024-06-05 21:52 ` Junio C Hamano
2024-06-05 21:39 ` Rubén Justo
2024-06-07 16:29 ` [PATCH v4 0/2] " Rubén Justo
2024-06-07 16:30 ` [PATCH v4 1/2] t4014: cleanups in a few tests Rubén Justo
2024-06-07 17:14 ` Junio C Hamano
2024-06-07 17:38 ` Rubén Justo
2024-06-07 18:57 ` Junio C Hamano
2024-06-07 16:30 ` [PATCH v4 2/2] format-patch: assume --cover-letter for diff in multi-patch series Rubén Justo
2024-06-07 20:52 ` [PATCH v5 0/2] " Rubén Justo
2024-06-07 20:55 ` [PATCH v5 1/2] t4014: cleanups in a few tests Rubén Justo
2024-06-07 20:55 ` [PATCH v5 2/2] format-patch: assume --cover-letter for diff in multi-patch series Rubén Justo
2024-06-07 21:10 ` [PATCH v5 0/2] " 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=xmqqbk4fs185.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
--cc=rjusto@gmail.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).