tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Mattijs Korpershoek <mkorpershoek@baylibre.com>
Cc: Guillaume Ranquet <granquet@baylibre.com>, tools@linux.kernel.org
Subject: Re: b4 send: missing diffstat in individual patches
Date: Thu, 22 Sep 2022 14:03:08 -0400	[thread overview]
Message-ID: <20220922180308.ap6bi2qcbxmeovmq@meerkat.local> (raw)
In-Reply-To: <87mtarfov3.fsf@baylibre.com>

On Thu, Sep 22, 2022 at 04:46:56PM +0200, Mattijs Korpershoek wrote:
> > 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.
> 
> Thank you for all the work you've put in the "contributor" side of b4.
> Your responsive replies and fixes are really appreciated, and so
> is the new documentation.

I'm glad people are using it! I'm sure there will be a lot of changes to my
initial implementation, and that was entirely expected.

Best regards,
Konstantin

      reply	other threads:[~2022-09-22 18:03 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
2022-09-22 14:46     ` Mattijs Korpershoek
2022-09-22 18:03       ` Konstantin Ryabitsev [this message]

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=20220922180308.ap6bi2qcbxmeovmq@meerkat.local \
    --to=konstantin@linuxfoundation.org \
    --cc=granquet@baylibre.com \
    --cc=mkorpershoek@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).