From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>,
"Signed-off-by: Stephen Rothwell" <sfr@canb.auug.org.au>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: b4 commit in -next breaks b4 on next
Date: Thu, 26 Sep 2024 09:43:23 +0100 [thread overview]
Message-ID: <f0289901-7d8a-403c-9ef4-c4927f2ea866@linaro.org> (raw)
In-Reply-To: <20240925-tentacled-porpoise-from-sirius-f442be@lemur>
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
prev parent reply other threads:[~2024-09-26 8:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 16:31 b4 commit in -next breaks b4 on next Bryan O'Donoghue
2024-09-25 20:11 ` Konstantin Ryabitsev
2024-09-26 8:43 ` Bryan O'Donoghue [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=f0289901-7d8a-403c-9ef4-c4927f2ea866@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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