1 |
On 8.1.2022 7.12, Sam James wrote: |
2 |
> |
3 |
> FWIW, normally we don't post individual package patches |
4 |
> to this ML, but it's a good question as to.. where they should go |
5 |
> if people want to use git send-email/a ML workflow. |
6 |
> |
7 |
> Right now, sometimes people send them to gentoo-proxy-maint |
8 |
> (the list) which the proxy maintainers team that handles |
9 |
> most user contributions looks at, but I'll be honest and say |
10 |
> our workflow isn't really optimised for it given it's used |
11 |
> pretty infrequently. |
12 |
> |
13 |
> Makes me wonder if we should rename the list |
14 |
> or have a separate one (gentoo-patches?). |
15 |
> |
16 |
> (Or just use that list and make sure people CC |
17 |
> maintainers as you did here?) |
18 |
> |
19 |
> Best, |
20 |
> sam |
21 |
|
22 |
I don't think setting up a new mailing list purely for patches will |
23 |
benefit much. It all comes down to who's gonna merge the contributions, |
24 |
and Github/bugzilla are definitely easier in that regard. I suggest |
25 |
opening a bug like normally, and then sending the .patch to the |
26 |
maintainers directly via e-mail with bug #nr linked either in Subject or |
27 |
git message body. |
28 |
|
29 |
-- juippis |