public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Adrian Ratiu <adrian.ratiu@collabora.com>
Cc: gentoo-dev@lists.gentoo.org, vapier@chromium.org,
	Lars Wendler <polynomial-c@gentoo.org>,
	proxy-maint@gentoo.org
Subject: [gentoo-dev] Mailing list for ebuild patches? (Was: Re: [PATCH] media-libs/freetype: fix GCC usage during configure)
Date: Sat, 8 Jan 2022 05:12:37 +0000	[thread overview]
Message-ID: <5D7C8FB1-600D-4C3A-9BCA-4CE22DDC8969@gentoo.org> (raw)
In-Reply-To: <20220107130813.1655260-1-adrian.ratiu@collabora.com>


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



> On 7 Jan 2022, at 13:08, Adrian Ratiu <adrian.ratiu@collabora.com> wrote:
> 
> If $CC_BUILD is not set, configure defaults to GCC for some
> of its tests causing clang builds to use a mixture of the
> two compilers instead of using just clang consistently.
> [snip]

Thanks!

Looks like Polynomial-C applied this as https://github.com/gentoo/gentoo/commit/355c5b5715ffcf787c421d03209642d2823cf1f7 <https://github.com/gentoo/gentoo/commit/355c5b5715ffcf787c421d03209642d2823cf1f7>.

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

[-- Attachment #1.2: Type: text/html, Size: 2185 bytes --]

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

  reply	other threads:[~2022-01-08  5:13 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 ` Sam James [this message]
2022-01-08  6:15   ` [gentoo-dev] Mailing list for ebuild patches? (Was: Re: [PATCH] media-libs/freetype: fix GCC usage during configure) Anna Vyalkova
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=5D7C8FB1-600D-4C3A-9BCA-4CE22DDC8969@gentoo.org \
    --to=sam@gentoo.org \
    --cc=adrian.ratiu@collabora.com \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=polynomial-c@gentoo.org \
    --cc=proxy-maint@gentoo.org \
    --cc=vapier@chromium.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