--Apple-Mail=_24EF3F33-1CDF-4AEF-9F39-09938F0A96E7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
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
--Apple-Mail=_24EF3F33-1CDF-4AEF-9F39-09938F0A96E7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=us-ascii
<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""
<div class="">On 7 Jan 2022, at 13:08, Adrian Ratiu <<a href="mailto:adrian.ratiu@collabora.com" class="">adrian.ratiu@collabora.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">If $CC_BUILD is not set,
configure defaults to GCC for some<br class="">of its tests causing clang builds to use a mixture of the<br class="">two compilers instead of using just clang consistently.<br class=""></div></div></blockquote><blockquote type="cite" class=""><div class="
"><div class="">[snip]</div></div></blockquote></div><br class=""><div class="">Thanks!</div><div class=""><br class=""></div><div class="">Looks like Polynomial-C applied this as <a href="
https://github.com/gentoo/gentoo/commit/
355c5b5715ffcf787c421d03209642d2823cf1f7" class="">
https://github.com/gentoo/gentoo/commit/355c5b5715ffcf787c421d03209642d2823cf1f7</a>.</div><div class=""><br class=""></div><div class="">FWIW, normally we don't post individual package patches</div><div
class="">to this ML, but it's a good question as to.. where they should go</div><div class="">if people want to use git send-email/a ML workflow.</div><div class=""><br class=""></div><div class="">Right now, sometimes people send them to gentoo-proxy-
maint</div><div class="">(the list) which the proxy maintainers team that handles</div><div class="">most user contributions looks at, but I'll be honest and say</div><div class="">our workflow isn't really optimised for it given it's used</div><div
class="">pretty infrequently.</div><div class=""><br class=""></div><div class="">Makes me wonder if we should rename the list</div><div class="">or have a separate one (gentoo-patches?).</div><div class=""><br class=""></div><div class="">(Or just use
that list and make sure people CC</div><div class="">maintainers as you did here?)</div><div class=""><br class=""></div><div class="">Best,</div><div class="">sam</div></body></html>
--Apple-Mail=_24EF3F33-1CDF-4AEF-9F39-09938F0A96E7--
-----BEGIN PGP SIGNATURE-----
iQGTBAEBCgB9FiEEYOpPv/uDUzOcqtTy9JIoEO6gSDsFAmHZHUVfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYw RUE0RkJGRkI4MzUzMzM5Q0FBRDRGMkY0OTIyODEwRUVBMDQ4M0IACgkQ9JIoEO6g SDvjJgf/UKbNz3x3skpjff/As1l5Fe6uKoP/Lw/0ZfdJotmwNxO7Xrhf3550SvTE iY4WVHOZ24e+5KAeurqIapgxKfMxpRPIsueMd51vXwp79trkmY2d9ww4SO6XAhvk IPijE7dq7zWVSFUhaDmWgV96HLj549BviWGCm4OzV/f3gu3SlwKg5XMA3caE8P5e 1cU7pEdBNYuUv5UWhFPsuhrDFeEhPmBtE4oO1x80KlSQocYLQ8JCzzmyHO4Lr9QS ODvTK7TvjEtc9f24e19RJFXJQULCxffEZjMi8LllnXIgoVDnbG7Pxw1ofCeFGzAU yLKTir0B6QrplIxK2ly9sP3MDHslgA==
=i2ac
-----END PGP SIGNATURE-----
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)