b4 review base commit isshes

Mark Brown <[email protected]> Tue, 30 Jun 2026 18:12:21 +0100
Newsgroups org.kernel.linux.tools
Message-ID <[email protected]>
Hi Konstantin,

I've run into a few issues recently where b4 has applied a series on a
merge base I am fairly sure I didn't expect - I *think* there is some
lag between me entering a merge base in the UI and it actually being
paid attention to, possibly if checks are ongoing while I'm editing the
UI.

Relatedly it's not really visible in the UI what the base for a series
is, I've only noticed this from the diffstat when applying which would
be even more annoying if it got as far as testing after I've applied a
bunch more things on top.

Something I did in my custom stuff is that I'd only pay attention to
base commits specified in the series if they were on specifically
approved branches, that way the common case where someone says they
based on -next doesn't cause -next to get pulled in by mistake.

Thanks,
Mark
signature.asc (application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmpD+PQACgkQJNaLcl1U
h9ClNgf/XEN68wmt+nH4nvkUKJuVrAMLtBeu9TdGWN5ZtfRUWkzKegLelaCMVeB0
9EGULQutT2CrrXkLKYxTNybRpyjA+1ZxN5KSYR/hQfq2QWrxxKMzWIT6bWovY2c3
HkAR1ZTYIIvXurQifpFBycsCcn6R6EIiRaR+rmdQ8Vh6tGWUuo40pfmuXgjbX+xD
BHjorNNisJexduk7aI9U1jS0p148vRCfJ1rEBsPMHfKGZBSz4Hd32ZGZQkMX66Wk
EPi7FsD5GDZCCE8fcSjj5JN+hehIhYVIceC/uXpS0AqKxBBFP/Ou6Cr6QTjE589O
jhxMfv9tonIY8/PvPPsMnQJoMGHZZQ==
=itAV
-----END PGP SIGNATURE-----