On 4/30/24 11:26, Yu Kuai wrote:
Hi,
在 2024/04/26 16:22, Mariusz Tkaczyk 写道:
On Fri, 26 Apr 2024 08:27:44 +0100
Wols Lists <antlists@xxxxxxxxxxxxxxx> wrote:
On 24/04/2024 13:27, Paul E Luse wrote:
* Instead of using the mailing list to propose patches, use GitHub Pull
Requests. Mariusz is setting up GitHub to send an email to the
mailing
list so that everyone can still be made aware of new patches in the
same manner as before. Just use GitHub moving forward for actual
code reviews.
Does that mean contributors now need a github account? That won't go
down well with some people I expect ...
Cheers,
Wol
Hi Wol,
There are thousands repositories on Github you have to register to
participate
and I don't believe that Linux developers may don't have Github
account. It is
almost impossible to not have a need to sent something to Github.
Will it still be able to send and apply patches through maillist? It's
important for us because I just can't create pr at GitHub in my
company, already tried with Paul, due to our company policy. :(
Although I can do this at home...
I do think this is a valid point.
(Having been in Beijing recently I do share the pain from Kuai :-)
We really should keep the mailing list alive, and enable people
to choose which interface suits them best.
I don't have a problem in switching to github as the primary
tree, but we should keep the original location intact as a
mirror and continue to allow people to use the mailing list
to send patches.
This is especially important for low-volume mailing lists,
where we have quite a few occasional contributors, and we
should strive to make it as easy (and convenient) as possible
for them.
Cheers,
Hannes
Here some examples:
https://github.com/iovisor/bcc
https://github.com/axboe/fio
https://github.com/dracutdevs/dracut
https://github.com/util-linux/util-linux
https://github.com/bpftrace/bpftrace
https://github.com/systemd/systemd
I see this as not a problem.
Thanks,
Mariusz
.
