Re: b4 v0.7.0 is available

[Konstantin Ryabitsev <konstantin@linuxfoundation.org>]

On Wed, May 26, 2021 at 04:41:17PM -0300, Jason Gunthorpe wrote:
> > It is very easy to start signing patches with patatt, so I invite everyone to
> > test it out. If you are using git-send-email, you can automate the whole thing
> > to happen behind the scenes via the sendemail-validate hook:
> > https://pypi.org/project/patatt/#getting-started-as-contributor
> 
> Any thoughts about connecting this to the patchwork instances?
> 
> As I patchwork user I've been wondering if I should be switching to
> fetch patches to apply via b4 instead via patchworks - would
> appreciate some clarity :)

The main difficulties with making it part of patchwork proper is mostly due to
it breaking the end-to-end nature of attestation: if we change patchwork to
perform the attestation check on the backend, we're back to trusting
kernel.org infrastructure. That is specifically something we want to get away
with. :)

We already do use patchwork-style patch hashes in b4, so perhaps a better
approach would be to closer integrate b4 with patchwork -- if simply on the
level of:

- list outstanding series in a patchwork project and retrieve them from lore
- automatically recognize patches that got applied and set their remote state
  to "Accepted"

I think this alone will help closer integrate the two workflows and avoid
needing to perform the attestation check on inherently untrusted
infrastructure.

-K