From: Junio C Hamano <gitster@pobox.com>
To: Pablo Sabater <pabloosabaterr@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [GSoC PATCH] format-patch: write numbered list in cover letter
Date: Mon, 09 Mar 2026 21:54:28 -0700 [thread overview]
Message-ID: <xmqqo6kwxp17.fsf@gitster.g> (raw)
In-Reply-To: <20260310041929.1687483-1-pabloosabaterr@gmail.com> (Pablo Sabater's message of "Tue, 10 Mar 2026 05:19:29 +0100")
Pablo Sabater <pabloosabaterr@gmail.com> writes:
> Cover letter generated with 'git format-patch --cover-letter' uses
> shortlog grouping commits by author. For a single author patch grouping
> by author add useless information and makes it hard to follow patch
> references: "second patch does x and y patch does z"
>
> Replace the shortlog with a numbered list of patches:
>
> [1/2]: first commit
> [2/2]: second commit
>
> shortlog grouping by author is lost, both for single author patches
> and multiple author patches
>
> suggested as #leftoverbits by Junio C Hamano at
> https://lore.kernel.org/git/xmqqbjhjxp2d.fsf@gitster.g/
>
> Signed-off-by: Pablo Sabater <pabloosabaterr@gmail.com>
> ---
> I haven't tried to group by author on multiple authors patches to keep it simple
> but I believe it's doable.
How does this compare with
https://lore.kernel.org/git/cover.1772839973.git.mroik@delayed.space/
I wonder.
next prev parent reply other threads:[~2026-03-10 4:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 4:19 [GSoC PATCH] format-patch: write numbered list in cover letter Pablo Sabater
2026-03-10 4:54 ` Junio C Hamano [this message]
2026-03-10 15:05 ` Pablo
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=xmqqo6kwxp17.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pabloosabaterr@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 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.