From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <gentoo-dev+bounces-96466-garchives=archives.gentoo.org@lists.gentoo.org> Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 7D3DC158087 for <garchives@archives.gentoo.org>; Mon, 17 Jan 2022 16:10:41 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8C9F52BC043; Mon, 17 Jan 2022 16:10:34 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 9CDD52BC03C for <gentoo-dev@lists.gentoo.org>; Mon, 17 Jan 2022 16:10:33 +0000 (UTC) Message-ID: <c0adba6e-8b66-0cff-a46a-cdb7b3b44d85@gentoo.org> Date: Mon, 17 Jan 2022 18:10:28 +0200 Precedence: bulk List-Post: <mailto:gentoo-dev@lists.gentoo.org> List-Help: <mailto:gentoo-dev+help@lists.gentoo.org> List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org> List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org> List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org> X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: [gentoo-dev] Mailing list for ebuild patches? (Was: Re: [PATCH] media-libs/freetype: fix GCC usage during configure) Content-Language: en-US To: gentoo-dev@lists.gentoo.org References: <20220107130813.1655260-1-adrian.ratiu@collabora.com> <5D7C8FB1-600D-4C3A-9BCA-4CE22DDC8969@gentoo.org> From: Joonas Niilola <juippis@gentoo.org> In-Reply-To: <5D7C8FB1-600D-4C3A-9BCA-4CE22DDC8969@gentoo.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------z1vVOLKjSws0qcRuN0f7ptZn" X-Archives-Salt: 1ab3e309-bbda-4606-84dc-df3b64c8d51d X-Archives-Hash: a370b226e1f151d0e6e8c7a717abcdad This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------z1vVOLKjSws0qcRuN0f7ptZn Content-Type: multipart/mixed; boundary="------------JIpUp8ojHtT2iRQbpeAl0PMA"; protected-headers="v1" From: Joonas Niilola <juippis@gentoo.org> To: gentoo-dev@lists.gentoo.org Message-ID: <c0adba6e-8b66-0cff-a46a-cdb7b3b44d85@gentoo.org> Subject: Re: [gentoo-dev] Mailing list for ebuild patches? (Was: Re: [PATCH] media-libs/freetype: fix GCC usage during configure) References: <20220107130813.1655260-1-adrian.ratiu@collabora.com> <5D7C8FB1-600D-4C3A-9BCA-4CE22DDC8969@gentoo.org> In-Reply-To: <5D7C8FB1-600D-4C3A-9BCA-4CE22DDC8969@gentoo.org> --------------JIpUp8ojHtT2iRQbpeAl0PMA Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 8.1.2022 7.12, Sam James wrote: >=20 > 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. >=20 > 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. >=20 > Makes me wonder if we should rename the list > or have a separate one (gentoo-patches?). >=20 > (Or just use that list and make sure people CC > maintainers as you did here?) >=20 > 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 --------------JIpUp8ojHtT2iRQbpeAl0PMA-- --------------z1vVOLKjSws0qcRuN0f7ptZn Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEltRJ9L6XRmDQCngHc4OUK43AaWIFAmHllPRfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDk2 RDQ0OUY0QkU5NzQ2NjBEMDBBNzgwNzczODM5NDJCOERDMDY5NjIACgkQc4OUK43A aWLg5Qf/RAdaAYcg2FTkagGz7KJ9bIkk4YhefNOEXBteoV/E/TLTqw0hMJ3koc5o SRvI0QGipUZTT6ngklKsOa2vX019sY/fAel32quFtkXYHBOZn1m9nSG6BWYECOe4 VBb/aPkLy0VNapFOa4kW4fdDb0BXRebVXZnQJPlvg813dVcxu/9cR8uMS2EMqJsk Ko/MBZ7ye0eckFnnZ36dvENNfZmqDyBOFukNQw8iyoQcNRpSXCVrBzPD8EIhzjMd ngAApOlRMQt9OQtpg5cYTGYLa1L7n4/X/RAVuLcOba1E33nBD063Mw0r+n2Ph4qM yYjTTtEKpDLgj40n9ceP0gC3MlrEmg== =J12i -----END PGP SIGNATURE----- --------------z1vVOLKjSws0qcRuN0f7ptZn--