From: Anna Vyalkova <cyber+gentoo@sysrq.in>
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)
Date: Sat, 8 Jan 2022 11:15:02 +0500 [thread overview]
Message-ID: <Ydkr5v10roYetCXF@sysrq.in> (raw)
In-Reply-To: <5D7C8FB1-600D-4C3A-9BCA-4CE22DDC8969@gentoo.org>
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.
next prev parent reply other threads:[~2022-01-08 6:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 13:08 [gentoo-dev] [PATCH] media-libs/freetype: fix GCC usage during configure Adrian Ratiu
2022-01-08 5:12 ` [gentoo-dev] Mailing list for ebuild patches? (Was: Re: [PATCH] media-libs/freetype: fix GCC usage during configure) Sam James
2022-01-08 6:15 ` Anna Vyalkova [this message]
2022-01-17 16:10 ` Joonas Niilola
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Ydkr5v10roYetCXF@sysrq.in \
--to=cyber+gentoo@sysrq.in \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox