LWN's guide to 2024
LWN's guide to 2024
Posted Jan 2, 2024 23:33 UTC (Tue) by iabervon (subscriber, #722)Parent article: LWN's guide to 2024
Posted Jan 3, 2024 5:15 UTC (Wed)
by mricon (subscriber, #59252)
[Link] (4 responses)
https://lore.kernel.org/tools/20231213-fluffy-roaring-cap...
It uses the email bridge as a mechanism to do additional code review and collect sign-offs from people who may not necessarily have an account on that particular forge.
I hope to work on this in the next few weeks.
Posted Jan 3, 2024 11:19 UTC (Wed)
by dullfire (guest, #111432)
[Link] (3 responses)
Is there any tooling for if going the other way, that is I use a mail client (or basically any other interface that doesn't require a github account or agreeing to github's ToS) to contribute?
I am sort of guessing not (for one, I suspect that would itself be a violation of github's ToS), but I thought I'd ask.
Posted Jan 3, 2024 20:49 UTC (Wed)
by rincebrain (subscriber, #69638)
[Link] (2 responses)
Posted Jan 3, 2024 21:22 UTC (Wed)
by iabervon (subscriber, #722)
[Link] (1 responses)
The forge and the email list probably have to be able to trust each other to have done the appropriate authentication of the attribution of review comments before transforming them in ways that preserve the meaning, which probably requires some sort of special agreement to be not too awkward.
I guess it might be okay to have the GitHub PR get a lot of review comments by kernel.org that say "according to (link to lore), (real person) says: (extracted comment about that part)", which kernel.org could add on its own behalf.
Posted Jan 7, 2024 18:10 UTC (Sun)
by mathstuf (subscriber, #69389)
[Link]
LWN's guide to 2024
LWN's guide to 2024
LWN's guide to 2024
LWN's guide to 2024
LWN's guide to 2024