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

[Laurent Pinchart]

On Tue, Jul 30, 2024 at 10:53:31AM +0200, Quentin Schulz wrote:
> On 7/30/24 10:11 AM, Milan Zamazal wrote:
> > 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?
> 
> If maintainers were to use b4 at some point in the future, they could use
> b4 ty
> I believe (I'm not a maintainer and not using b4 for maintaining stuff, 
> so just reading the b4 usage from b4 --help :) ).
> 
> I agree, this is something I really appreciate from kernel development 
> and miss with Yocto/OE development. I don't contribute to libcamera, 
> rather monitor what's happening to interesting patches but I would 
> probably miss it the same way.

As long as patches are reviewed over e-mail, I think notifying by e-mail
makes sense. We should even be able to automatically update patchwork.

I'll try to have a look at this without waiting for too long, but there
are always things preempting devops. Is there anyone on this list who
would consider it fun to implement all this ? :-)

-- 
Regards,

Laurent Pinchart