From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 8EB0D158086 for ; Sat, 8 Jan 2022 06:15:30 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 06B4A2BC013; Sat, 8 Jan 2022 06:15:10 +0000 (UTC) Received: from sysrq.in (sysrq.in [37.79.202.136]) (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 003EBE07A5 for ; Sat, 8 Jan 2022 06:15:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sysrq.in; s=sysrq.in; t=1641622503; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=A73Bxsp6l8gHidLRGnA0xhoElRDuaDXUc49hWPAMtUw=; b=o8s4pC2Cs12QrqxDfB1cEnJOnw++v62lP9uir75nQFdHAUz8S++soJLXwWxGFt7jNdNGUn YCyxBr2YKRPXx7CInKBOdoEKT3I20TPyF1hLJ4gE/PYSgaIatg9hsbPBESBCQVYq9B7A+F sV55G0mgM7BSmkFpHZRmYHhUr8mA8VElMH97mVlK0xm6qkPNxQcfWWExqiKH5fqCFynOQc 00PFcfx0Nk52Y1ztJJkl1MQ1mLL9sAwertqVsMebJllK/HAkQOn3tdULU08lVXlVSgiEd2 7Xb4QpZJeyAZi3whs9858BvuFu7mHi/sQhzKNrASB0cUO2+JvqwJRC/ysnNBdA== Received: from sysrq.in (localhost [127.0.0.1]) by sysrq.in (OpenSMTPD) with ESMTPSA id 1f20ce24 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Sat, 8 Jan 2022 06:15:03 +0000 (UTC) Date: Sat, 8 Jan 2022 11:15:02 +0500 From: Anna Vyalkova To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Mailing list for ebuild patches? (Was: Re: [PATCH] media-libs/freetype: fix GCC usage during configure) Message-ID: Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <20220107130813.1655260-1-adrian.ratiu@collabora.com> <5D7C8FB1-600D-4C3A-9BCA-4CE22DDC8969@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5D7C8FB1-600D-4C3A-9BCA-4CE22DDC8969@gentoo.org> X-Archives-Salt: c58cfa7d-2527-42ab-a316-ff2a5bd319e1 X-Archives-Hash: b318854b83d0dd4e88afa522c813d250 On 2022-01-08 05: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. Sending patches directly to maintainer(s) also works for git send-email workflow. > Makes me wonder if we should rename the list > or have a separate one (gentoo-patches?). I think gentoo-patches will only be useful if it's low-traffic, otherwise devs may be unwilling to subscribe and pay attention to it.