Nemeski to [email protected] • 2 months agoThe graying open source community needs fresh bloodwww.theregister.comexternal-linkmessage-square86fedilinkarrow-up1318arrow-down13
arrow-up1315arrow-down1external-linkThe graying open source community needs fresh bloodwww.theregister.comNemeski to [email protected] • 2 months agomessage-square86fedilink
minus-squareim sorry i broke the codelink17•2 months agoHow do you contribute code through a mailing list? Like I don’t understand…
minus-square@[email protected]linkfedilinkEnglish22•2 months agoFound a blog post that gives a quick overview of how to do git via email in general: https://peter.eisentraut.org/blog/2023/05/09/how-to-submit-a-patch-by-email-2023-edition So at least from my understanding you’d make your changes, email the contents of the patch to the maintainer, and then they’d apply it on their side, do code review, email you comments, etc. until it was in an acceptable state. There’s also the full kernel development wiki that goes into all the specifics: https://www.kernel.org/doc/html/v4.16/process/howto.html (I never got through the whole thing)
minus-squareJackbyDevlinkfedilinkEnglish10•edit-22 months agoELI5: Git has tools built-in to put your changes into emails and send them. People can either bring them in or see the diff in the emails. Reading and interactive tutorials: https://useplaintext.email/ https://git-send-email.io/
minus-square@[email protected]linkfedilink4•2 months agoAwkwardly. Pretty much generate a patch and email it as an attachment.
minus-squareEager EaglelinkfedilinkEnglish2•2 months agoby writing your diffs with red and black ink, like the Aztecs did
How do you contribute code through a mailing list? Like I don’t understand…
Found a blog post that gives a quick overview of how to do git via email in general: https://peter.eisentraut.org/blog/2023/05/09/how-to-submit-a-patch-by-email-2023-edition
So at least from my understanding you’d make your changes, email the contents of the patch to the maintainer, and then they’d apply it on their side, do code review, email you comments, etc. until it was in an acceptable state.
There’s also the full kernel development wiki that goes into all the specifics: https://www.kernel.org/doc/html/v4.16/process/howto.html
(I never got through the whole thing)
ELI5: Git has tools built-in to put your changes into emails and send them. People can either bring them in or see the diff in the emails.
Reading and interactive tutorials:
Awkwardly. Pretty much generate a patch and email it as an attachment.
by writing your diffs with red and black ink, like the Aztecs did