From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: kh/format-patch-range-diff-notes
Date: Tue, 22 Sep 2026 10:11:26 +0200 [thread overview]
Message-ID: <92ae04ac-6e94-4785-ae51-dbe794c07fad@app.fastmail.com> (raw)
In-Reply-To: <xmqqwlsei1pv.fsf@gitster.g>
On Tue, Sep 22, 2026, at 02:11, Junio C Hamano wrote:
> * kh/format-patch-range-diff-notes (2026-08-24) 3 commits
> . format-patch: learn --[no-]range-diff-notes
> . revision.h: rename struct member to reflect notes role
> . format-patch: simplify get_notes_arg parameters
>
> The 'format-patch' command has been updated with options to
> configure notes specifically for range-diff output, allowing them to
> differ from the notes displayed on the patches themselves.
>
> Expecting a reroll.
> cf. <8f0a076b-4822-44e2-a842-cc1e39ae1c1d@app.fastmail.com>
> source: <CV_format-patch_learn_--range-diff-notes.c57@msgid.xyz>
I’ll comment since it’s almost been a month. It’s a straightforward
reroll but I haven’t been able to do the about hour’s worth of work.
I should get some time at the latest on the weekend.
next prev parent reply other threads:[~2026-09-22 8:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 0:11 What's cooking in git.git (Sep 2026, #08) Junio C Hamano
2026-09-22 8:11 ` Kristoffer Haugsbakk [this message]
2026-09-22 13:25 ` Git v3.0 timeline, was " Johannes Schindelin
2026-09-22 13:49 ` Junio C Hamano
2026-09-22 17:06 ` Johannes Schindelin
2026-09-24 3:56 ` Junio C Hamano
2026-09-24 4:30 ` Junio C Hamano
2026-09-24 12:29 ` Johannes Schindelin
2026-09-24 17:00 ` Junio C Hamano
2026-09-24 18:08 ` Ramsay Jones
2026-09-22 18:44 ` My summary of the Git Contributors' Summit 2026, was " Johannes Schindelin
2026-09-23 11:55 ` Daniele Sassoli
2026-09-24 12:31 ` Johannes Schindelin
2026-09-25 9:53 ` Luca Milanesio
2026-09-23 12:52 ` D. Ben Knoble
2026-09-23 14:22 ` Security mailing list & process, was Re: My summary of the Git Contributors' Summit 2026 Toon Claes
2026-09-24 12:38 ` Johannes Schindelin
2026-09-23 14:40 ` Git Contributor' summit: Documentation, was: Re: My summary of the Git Contributors' Summit 2026, was Re: Git v3.0 timeline, was Re: What's cooking in git.git (Sep 2026, #08) Toon Claes
2026-09-23 15:15 ` Git Contributor' summit: Documentation, Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2026-09-04 23:55 What's cooking in git.git (Sep 2026, #02) Junio C Hamano
2026-09-05 6:31 ` kh/format-patch-range-diff-notes Kristoffer Haugsbakk
2026-08-26 23:21 What's cooking in git.git (Aug 2026, #11) Junio C Hamano
2026-08-27 6:06 ` kh/format-patch-range-diff-notes Kristoffer Haugsbakk
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=92ae04ac-6e94-4785-ae51-dbe794c07fad@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.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