* b4 commit in -next breaks b4 on next
@ 2024-09-25 16:31 Bryan O'Donoghue
2024-09-25 20:11 ` Konstantin Ryabitsev
0 siblings, 1 reply; 3+ messages in thread
From: Bryan O'Donoghue @ 2024-09-25 16:31 UTC (permalink / raw)
To: Jiri Kosina, Benjamin Tissoires, Signed-off-by: Stephen Rothwell; +Cc: lkml
Hey.
On commit 2b7275670032a98cba266bd1b8905f755b3e650f (HEAD ->
b4/master-24-11-25-ov08x40, tag: next-20240925, linux-next/master)
exists
commit 3a904d2c771115154380caaae7ffaaf0095fb88f
Author: Benjamin Tissoires <bentiss@kernel.org>
Date: Fri Jul 5 14:07:06 2024 +0200
HID: fix for amples in for-6.11/bpf
To: Jiri Kosina <jikos@kernel.org>
Cc: linux-input@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Benjamin Tissoires <bentiss@kernel.org>
---
Changes in v2:
- EDITME: describe what is new in this series revision.
- EDITME: use bulletpoints and terse descriptions.
- Link to v1:
https://lore.kernel.org/r/20240705-for-6-11-bpf-v1-1-1960e3165c9e@kernel.org
--- b4-submit-tracking ---
# This section is used internally by b4 prep for tracking purposes.
{
"series": {
"revision": 2,
"change-id": "20240705-for-6-11-bpf-a349efc08df8",
"prefixes": [],
"history": {
"v1": [
"20240705-for-6-11-bpf-v1-1-1960e3165c9e@kernel.org"
]
}
}
}
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.
---
bod
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: b4 commit in -next breaks b4 on next
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
0 siblings, 1 reply; 3+ messages in thread
From: Konstantin Ryabitsev @ 2024-09-25 20:11 UTC (permalink / raw)
To: Bryan O'Donoghue
Cc: Jiri Kosina, Benjamin Tissoires, Signed-off-by: Stephen Rothwell,
lkml
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: b4 commit in -next breaks b4 on next
2024-09-25 20:11 ` Konstantin Ryabitsev
@ 2024-09-26 8:43 ` Bryan O'Donoghue
0 siblings, 0 replies; 3+ messages in thread
From: Bryan O'Donoghue @ 2024-09-26 8:43 UTC (permalink / raw)
To: Konstantin Ryabitsev
Cc: Jiri Kosina, Benjamin Tissoires, Signed-off-by: Stephen Rothwell,
lkml
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-09-26 8:43 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox