Re: [gentoo-dev] Mailing list for ebuild patches? (Was: Re: [PATCH] media-libs/freetype: fix GCC usage during configure)

[Joonas Niilola <juippis@gentoo.org>]

[-- Attachment #1.1: Type: text/plain, Size: 1089 bytes --]

On 8.1.2022 7.12, Sam James wrote:
> 
> FWIW, normally we don't post individual package patches
> to this ML, but it's a good question as to.. where they should go
> if people want to use git send-email/a ML workflow.
> 
> Right now, sometimes people send them to gentoo-proxy-maint
> (the list) which the proxy maintainers team that handles
> most user contributions looks at, but I'll be honest and say
> our workflow isn't really optimised for it given it's used
> pretty infrequently.
> 
> Makes me wonder if we should rename the list
> or have a separate one (gentoo-patches?).
> 
> (Or just use that list and make sure people CC
> maintainers as you did here?)
> 
> Best,
> sam

I don't think setting up a new mailing list purely for patches will
benefit much. It all comes down to who's gonna merge the contributions,
and Github/bugzilla are definitely easier in that regard. I suggest
opening a bug like normally, and then sending the .patch to the
maintainers directly via e-mail with bug #nr linked either in Subject or
git message body.

-- juippis

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]