From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Guillaume Ranquet <granquet@baylibre.com>
Cc: tools@linux.kernel.org
Subject: Re: b4 send: missing diffstat in individual patches
Date: Thu, 22 Sep 2022 10:22:16 -0400 [thread overview]
Message-ID: <20220922142216.vpetai65om2bvv4l@meerkat.local> (raw)
In-Reply-To: <20220922132910.gz66mwjcdd7ljd6j@meerkat.local>
On Thu, Sep 22, 2022 at 09:29:10AM -0400, Konstantin Ryabitsev wrote:
> > 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.
>
> I'll try to put that in today.
This was an easy fix, so it's in master. I'll backport it into 0.10.y stable
later today.
-K
next prev parent reply other threads:[~2022-09-22 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 11:37 b4 send: missing diffstat in individual patches Guillaume Ranquet
2022-09-22 13:29 ` Konstantin Ryabitsev
2022-09-22 14:22 ` Konstantin Ryabitsev [this message]
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=20220922142216.vpetai65om2bvv4l@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=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).