tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rob Herring" <robh@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org, users@linux.kernel.org
Subject: Re: [kernel.org users] b4 v0.3.4 released
Date: Thu, 26 Mar 2020 10:11:44 -0600	[thread overview]
Message-ID: <CAL_JsqKBskO3oyEP0g9nTyWL4V614w21Hwigs5YpFpgLnUVktg@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqLJkDx3HQEN-0ih0Jp4i2h7xKYrsfqAiYcW_hV-9GtLKA@mail.gmail.com>

On Thu, Mar 26, 2020 at 10:04 AM Rob Herring <robh@kernel.org> wrote:
>
> On Mon, Mar 23, 2020 at 4:20 PM Konstantin Ryabitsev
> <konstantin@linuxfoundation.org> wrote:
> >
> > Hello:
> >
> > I pushed v0.3.4 to pypi, so if you're using it from there, you can run
> > "pip install --user --upgrade b4" to grab the latest version.
> >
> > Notable changes compared to 0.3.3:
> >
> > - deals properly with series versions that are only mentioned in the
> >   cover letter
> > - adds a b4.sh wrapper that lets you run b4 without needing to install
> >   with pip
> > - fixes a couple of backtraces due to bugs with patch attestation
> > - adds a caching layer to avoid hitting lore.kernel.org on repeating
> >   runs (e.g. when rerunning with -t, -s, -l, and similar)
> > - properly refuses to install on python version < 3.5
> > - uses more descriptive filenames for "b4 am" mboxes
>
> I'm seeing corruption of the subject on patches[1] with a comma in the
> subject (and I'd guess only ones longer than 70 something chars). It's
> fine on lore web interface, but it gets wrapped in the downloaded
> mbox. A log is attached. When it gets applied, a space is inserted
> after the comma:
>
> dt-bindings: iio/accel: Drop duplicate adi, adxl345/6 from trivial-devices.yaml

Nevermind. It's not b4, but the dri-devel list that is corrupting the subject.

https://lore.kernel.org/dri-devel/20200325220542.19189-2-robh@kernel.org/
https://lore.kernel.org/linux-devicetree/20200325220542.19189-2-robh@kernel.org/

Rob

> Interestingly, DT patchwork suffers from the same issue.
>
> Also, I got tripped up with missing acks again because dri-devel got
> picked and it moderates non-subscribers. A way to set the default
> project would be nice. Perhaps rather than a single default, making it
> a list of lists to try. Or trying lkml first might work better if
> we're just guessing.
>
> Rob
>
> [1] https://lore.kernel.org/linux-devicetree/20200325220542.19189-2-robh@kernel.org/

  reply	other threads:[~2020-03-26 16:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-23 22:20 b4 v0.3.4 released Konstantin Ryabitsev
2020-03-25  2:11 ` [kernel.org users] " Jason A. Donenfeld
2020-03-25  2:19   ` Jason A. Donenfeld
2020-03-25 15:05     ` Konstantin Ryabitsev
2020-03-25 15:26   ` Konstantin Ryabitsev
2020-03-26 16:04 ` Rob Herring
2020-03-26 16:11   ` Rob Herring [this message]
2020-03-26 16:16     ` Konstantin Ryabitsev
2020-03-26 16:27       ` James Bottomley
2020-03-26 16:31         ` Geert Uytterhoeven
     [not found]     ` <15FFE6D3B979AF4C.32445@linux.kernel.org>
2020-03-26 16:32       ` Konstantin Ryabitsev
2020-03-26 20:18         ` Jason A. Donenfeld
2020-03-27 18:15           ` Konstantin Ryabitsev
2020-04-06 21:53           ` Konstantin Ryabitsev
2020-09-22 22:17         ` Rob Herring

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=CAL_JsqKBskO3oyEP0g9nTyWL4V614w21Hwigs5YpFpgLnUVktg@mail.gmail.com \
    --to=robh@kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=tools@linux.kernel.org \
    --cc=users@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).