lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240925-tentacled-porpoise-from-sirius-f442be@lemur>
Date: Wed, 25 Sep 2024 16:11:21 -0400
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Bryan O'Donoghue <bryan.odonoghue@...aro.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 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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ