[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f0289901-7d8a-403c-9ef4-c4927f2ea866@linaro.org>
Date: Thu, 26 Sep 2024 09:43:23 +0100
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
Cc: Jiri Kosina <jikos@...nel.org>, Benjamin Tissoires <bentiss@...nel.org>,
"Signed-off-by: Stephen Rothwell" <sfr@...b.auug.org.au>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: b4 commit in -next breaks b4 on next
On 25/09/2024 21:11, Konstantin Ryabitsev wrote:
> On Wed, Sep 25, 2024 at 05:31:14PM GMT, Bryan O'Donoghue wrote:
>> Which means if you run "b4 prep --edit-cover" that is used as the base for
>> your b4 series.
>>
>> You can't revert 3a904d2c771115154380caaae7ffaaf0095fb88f so you basically
>> can't use -next for b4 at the moment.
>
> This should not be a problem with version 0.14.x. Are you using an older
> version of b4?
>
> -K
Ah
b4 --version
0.13-dev-26615
cd ~/Development/b4
git pull
b4 --version
0.15-dev-dedf8
Great, fixed thanks.
---
bod
Powered by blists - more mailing lists