1 |
> On 7 Jan 2022, at 13:08, Adrian Ratiu <adrian.ratiu@×××××××××.com> wrote: |
2 |
> |
3 |
> If $CC_BUILD is not set, configure defaults to GCC for some |
4 |
> of its tests causing clang builds to use a mixture of the |
5 |
> two compilers instead of using just clang consistently. |
6 |
> [snip] |
7 |
|
8 |
Thanks! |
9 |
|
10 |
Looks like Polynomial-C applied this as https://github.com/gentoo/gentoo/commit/355c5b5715ffcf787c421d03209642d2823cf1f7 <https://github.com/gentoo/gentoo/commit/355c5b5715ffcf787c421d03209642d2823cf1f7>. |
11 |
|
12 |
FWIW, normally we don't post individual package patches |
13 |
to this ML, but it's a good question as to.. where they should go |
14 |
if people want to use git send-email/a ML workflow. |
15 |
|
16 |
Right now, sometimes people send them to gentoo-proxy-maint |
17 |
(the list) which the proxy maintainers team that handles |
18 |
most user contributions looks at, but I'll be honest and say |
19 |
our workflow isn't really optimised for it given it's used |
20 |
pretty infrequently. |
21 |
|
22 |
Makes me wonder if we should rename the list |
23 |
or have a separate one (gentoo-patches?). |
24 |
|
25 |
(Or just use that list and make sure people CC |
26 |
maintainers as you did here?) |
27 |
|
28 |
Best, |
29 |
sam |