From: Junio C Hamano <gitster@pobox.com>
To: kristofferhaugsbakk@fastmail.com
Cc: git@vger.kernel.org, Kristoffer Haugsbakk <code@khaugsbakk.name>
Subject: Re: [PATCH 2/2] format-patch: handle range-diff on notes correctly for single patches
Date: Mon, 22 Sep 2025 15:01:25 -0700 [thread overview]
Message-ID: <xmqqecryrvt6.fsf@gitster.g> (raw)
In-Reply-To: <7f2487af433.1758574974.git.code@khaugsbakk.name> (kristofferhaugsbakk@fastmail.com's message of "Mon, 22 Sep 2025 23:10:23 +0200")
kristofferhaugsbakk@fastmail.com writes:
> From: Kristoffer Haugsbakk <code@khaugsbakk.name>
>
> No `--[no-]notes` options are sent to the range-diff subprocess in
> `range-diff.c` when making a single patch. This means that you can get
> different Git notes below the commit message and in the range-diff
> part. (See the previous commit for elaboration.)
Would this also mean "range-diff --no-notes" would not have any
effect in squelching the note output in such a mode? If so, perhaps
we should say not just "can get different Git notes" but "can get
notes even when you asked not to"?
> @@ -718,7 +718,8 @@ static void show_diff_of_diff(struct rev_info *opt)
> .creation_factor = opt->creation_factor,
> .dual_color = 1,
> .max_memory = RANGE_DIFF_MAX_MEMORY_DEFAULT,
> - .diffopt = &opts
> + .diffopt = &opts,
> + .other_arg = &opt->rdiff_other_arg
> };
>
> memcpy(&dq, &diff_queued_diff, sizeof(diff_queued_diff));
> diff --git a/t/t3206-range-diff.sh b/t/t3206-range-diff.sh
> index e091df6d01d..1e812df806b 100755
> --- a/t/t3206-range-diff.sh
> +++ b/t/t3206-range-diff.sh
> @@ -707,7 +707,7 @@ test_expect_success 'format-patch --range-diff does not compare notes by default
> ! grep "note" 0000-*
> '
>
> -test_expect_success 'format-patch --notes=custom --range-diff only compares custom notes' '
> +test_expect_success 'format-patch --notes=custom --range-diff --cover-letter only compares custom notes' '
> test_when_finished "git notes remove topic unmodified || :" &&
> git notes add -m "topic note" topic &&
> git notes add -m "unmodified note" unmodified &&
> @@ -721,6 +721,20 @@ test_expect_success 'format-patch --notes=custom --range-diff only compares cust
> ! grep "## Notes ##" 0000-*
> '
>
> +# --range-diff on a single commit requires --no-cover-letter
> +test_expect_success 'format-patch --notes=custom --range-diff on single commit only compares custom notes' '
> + test_when_finished "git notes remove HEAD unmodified || :" &&
> + git notes add -m "topic note" HEAD &&
> + test_when_finished "git notes --ref=custom remove HEAD unmodified || :" &&
> + git notes add -m "unmodified note" unmodified &&
> + git notes --ref=custom add -m "topic note (custom)" HEAD &&
> + git notes --ref=custom add -m "unmodified note (custom)" unmodified &&
> + git format-patch --notes=custom --range-diff=$prev \
> + -1 --stdout >actual &&
> + test_grep "## Notes (custom) ##" actual &&
> + test_grep ! "## Notes ##" actual
> +'
Sounds sensible.
> test_expect_success 'format-patch --range-diff with --no-notes' '
> test_when_finished "git notes remove topic unmodified || :" &&
> git notes add -m "topic note" topic &&
next prev parent reply other threads:[~2025-09-22 22:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 21:10 [PATCH 0/2] format-patch: handle range-diff on notes correctly for single patches kristofferhaugsbakk
2025-09-22 21:10 ` [PATCH 1/2] revision: add rdiff_other_arg to rev_info kristofferhaugsbakk
2025-09-22 21:58 ` Junio C Hamano
2025-09-23 15:53 ` Kristoffer Haugsbakk
2025-09-23 17:35 ` Junio C Hamano
2025-09-23 17:47 ` Kristoffer Haugsbakk
2025-09-23 21:18 ` Junio C Hamano
2025-09-22 21:10 ` [PATCH 2/2] format-patch: handle range-diff on notes correctly for single patches kristofferhaugsbakk
2025-09-22 22:01 ` Junio C Hamano [this message]
2025-09-23 16:26 ` Kristoffer Haugsbakk
2025-09-23 21:20 ` Junio C Hamano
2025-09-25 17:07 ` [PATCH v2 0/3] " kristofferhaugsbakk
2025-09-25 17:07 ` [PATCH v2 1/3] range-diff: rename other_arg to log_arg kristofferhaugsbakk
2025-09-25 17:07 ` [PATCH v2 2/3] revision: add rdiff_log_arg to rev_info kristofferhaugsbakk
2025-09-25 17:07 ` [PATCH v2 3/3] format-patch: handle range-diff on notes correctly for single patches kristofferhaugsbakk
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=xmqqecryrvt6.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.