Why are we using email patch review instead of GitLab merge requests?

[Milan Zamazal]

Laurent Pinchart <laurent.pinchart at ideasonboard.com> writes:

> For what it's worth, we would like to setup a public-inbox instance for
> libcamera, to enable usage of tools such as b4 and lei.

One thing I miss here is to know whether a patch (or series) is merged
or not.  I can obviously search in the repo but a notification attached
to the review thread or something similar would better fit the workflow.
Any idea?

> Another big issue that I mentioned is the difficulty to customize
> workflows. I will also call editing review comments and code in the
> git..b web UI "awful" unapologetically.
>
> You mentioned working on more than a single project, I actually find the
> mailing list workflow much better in that case. I get everything in a
> single e-mail client, I don't have to log in github.com, gitlab.com,
> gitlab.freedesktop.org and all the other ones independently. Until we
> get some federation protocol for forges with decent clients that don't
> run in web browsers, I'll have a hard time changing my mind.

At least for Emacs users, there are some add-ons that try to cope with
that by using the Emacs UI, with varying levels of success.

Regards,
Milan