Re: Problem with b4

[Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>]

On Tue, Apr 14, 2020 at 02:22:30PM +0200, Linus Walleij wrote:
> WARNING: Thread incomplete!
> Cover: ./v3_20200323_sergey_semin_gpio_dwapb_fix_reference_clocks_usage.cover
>  Link: https://lore.kernel.org/r/20200323195401.30338-1-Sergey.Semin@xxxxxxxxxxxxxxxxxxxx
>  Base: not found, sorry
>        git checkout -b v3_20200323_sergey_semin_baikalelectronics_ru master
>        git am ./v3_20200323_sergey_semin_gpio_dwapb_fix_reference_clocks_usage.mbx
> 
> This is weird because I am looking at the v3 version
> of patch [4/6] here for example:
> 
> https://lore.kernel.org/linux-gpio/20200323195401.30338-5-Sergey.Semin@xxxxxxxxxxxxxxxxxxxx/
> 
> It seems to be in-reply-to the right message and everything.
> 
> Can you tell me what I'm doing wrong?

Nothing, really -- the problem is that when we look up that message-id 
across all the lists we have, the first hit is on the devicetree list, 
and apparently only *some* of the patches were sent there. I have a fix 
for this in b4 v0.4.0 (not yet released):

...
Looking up https://lore.kernel.org/r/20200323195401.30338-1-Sergey.Semin%40baikalelectronics.ru
Grabbing thread from lore.kernel.org/linux-devicetree
Analyzing 14 messages in the thread
---
Thread incomplete, attempting to backfill
Grabbing thread from lore.kernel.org/linux-gpio
Loaded 16 messages from https://lore.kernel.org/linux-gpio/
Successfully backfilled missing patches
...
 
> I just installed b4 on this machine with pip3 install --user b4

I am not quite ready to release 0.4.0, so if you don't want to use b4 
straight out of git, you can pass `-p lkml` to the version you have 
installed from pip, an most of the time it should do the right thing.

I hope to have 0.4.0 out in the next few days.

-K