From: "James Bottomley" <James.Bottomley@HansenPartnership.com>
To: Linus Torvalds <torvalds@linuxfoundation.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: [kernel.org users] b4 version 0.5.0 is available
Date: Mon, 08 Jun 2020 10:30:47 -0700 [thread overview]
Message-ID: <1591637447.3500.15.camel@HansenPartnership.com> (raw)
In-Reply-To: <CAHk-=wipQzNyLxEh2mr2=Y9brLx_y0G0aKrVcjG2Ad3ba+_41Q@mail.gmail.com>
On Mon, 2020-06-08 at 09:59 -0700, Linus Torvalds wrote:
> Hmm.
>
> This fails with the most recent patch-bomb from Andrew when I
> randomly
> picked the email (just because it was most recent in my mailbox
> because of a reply, not because of arrival), and I don't see why.
>
> Doing
>
> b4 am 20200608044014.1sydER6sj%akpm@linux-foundation.org
>
> gets me 51 out of 54 patches, and no cover letter. Strange.
>
> But when I do the same on the _first_ message ID in the series:
>
> b4 am 20200608044004.04xI8ALrc%akpm@linux-foundation.org
>
> it gets the whole series. It again doesn't find the base commit, but
> it's a lot better.
That's an akpm problem: you can see it here on lore:
https://lore.kernel.org/linux-mm/20200608044004.04xI8ALrc%25akpm@linux-foundation.org/
Lore says it can't find the cover letter because the In-reply-to has
the wrong message id. This broke threading on my system as well.
James
next prev parent reply other threads:[~2020-06-08 17:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 20:33 b4 version 0.5.0 is available Konstantin Ryabitsev
2020-06-08 16:59 ` [kernel.org users] " Linus Torvalds
2020-06-08 17:30 ` James Bottomley [this message]
2020-06-08 17:59 ` Linus Torvalds
2020-06-08 18:06 ` 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=1591637447.3500.15.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.kernel.org \
--cc=torvalds@linuxfoundation.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 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.