Nemeski@lemm.ee to Programming@programming.dev · 4 months agoThe graying open source community needs fresh bloodwww.theregister.comexternal-linkmessage-square93fedilinkarrow-up1322cross-posted to: opensource@lemmit.online
arrow-up1322external-linkThe graying open source community needs fresh bloodwww.theregister.comNemeski@lemm.ee to Programming@programming.dev · 4 months agomessage-square93fedilinkcross-posted to: opensource@lemmit.online
minus-squareCMahaff@lemmy.worldlinkfedilinkEnglisharrow-up22·4 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)
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)