git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v3] format-patch: assume --cover-letter for diff in multi-patch series
Date: Wed, 05 Jun 2024 14:52:21 -0700	[thread overview]
Message-ID: <xmqqv82noy5m.fsf@gitster.g> (raw)
In-Reply-To: <5aebe520-e540-46b4-a887-af488fe2663a@gmail.com> ("Rubén Justo"'s message of "Wed, 5 Jun 2024 23:24:53 +0200")

Rubén Justo <rjusto@gmail.com> writes:

> I'm curious, a test like: 
>
> test_expect_success "format-patch --range-diff, implicit --cover-letter" '
> 	test_when_finished "rm v2-000?-*" &&
> 	test_must_fail git format-patch --no-cover-letter
> 		-v2 --range-diff=topic main..unmodified
>
> isn't it confusing?

It is, but what makes it confusing is that the title does not
describe what it tests, no?  It tests that --no-cover-letter
disables implicit cover-letter generation even with the presence of
--range-diff.

In the context of t3206-range-diff.sh, we know we are talking about
the "range-diff", and mention of "cover-letter" is a hint enough
that the "format-patch" is involved, so perhaps titles like

    test_expect_success 'explicit --no-cover-letter defeats implied --cover-letter'

and

    test_expect_success '--cover-letter is implied for multi-patch series'

would be clear enough and convey what the tests are actually doing.

  reply	other threads:[~2024-06-05 21:52 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
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 [this message]
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=xmqqv82noy5m.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).