From: Guillaume Ranquet <granquet@baylibre.com>
To: tools@linux.kernel.org
Subject: b4 send: missing diffstat in individual patches
Date: Thu, 22 Sep 2022 04:37:44 -0700 [thread overview]
Message-ID: <CABnWg9uBOGqJMq=yCtn7SoEME=+2u1-ZK9ftb6=_jRhkhL_jiw@mail.gmail.com> (raw)
Hello,
I've recently sent a patch series with b4 and diffstats are missing
from individual patches.
Which in itself is not an issue as I understand this is only comments
that are irrelevant to
the patch itself.
Though, I've had some complaints that my patches looks broken...
people seem to expect the
diffstat to be present.
The serie was sent with 0.10.0-dev (master from some weeks ago).
I've just retried a dry-run with the latest and the diffstat is still missing.
I haven't seen any option in b4 send to produce the individual commit
diffstat, I will have
a quick look if I can propose a patch.
Thx,
Guillaume.
next reply other threads:[~2022-09-22 11:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 11:37 Guillaume Ranquet [this message]
2022-09-22 13:29 ` b4 send: missing diffstat in individual patches Konstantin Ryabitsev
2022-09-22 14:22 ` Konstantin Ryabitsev
2022-09-22 14:46 ` Mattijs Korpershoek
2022-09-22 18:03 ` Konstantin Ryabitsev
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='CABnWg9uBOGqJMq=yCtn7SoEME=+2u1-ZK9ftb6=_jRhkhL_jiw@mail.gmail.com' \
--to=granquet@baylibre.com \
--cc=tools@linux.kernel.org \
/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).