Profitez des vidéos et de la musique que vous aimez, mettez en ligne des contenus originaux, et partagez-les avec vos amis, vos proches et le monde entier.
I actually prefer the e-mail patch based workflow over things pull/merge requests, it prevents me from having like 9 different accounts on 9 different Git forges.
I agree, and do think it is a matter of developer education. Most professional software engineers are familiar with the github/gitlab PR-based workflow. Unfortunately very few ever have occasion to use the email patch workflow unless they want to contribute to the linux kernel or something. Maybe something like this can bridge the gap but idk: https://pr.pico.sh/
Sourcehut actually has a nice website that walks you through how to send patches via e-mail with a mailing list & repository that you can experiment with. https://git-send-email.io/
I actually prefer the e-mail patch based workflow over things pull/merge requests, it prevents me from having like 9 different accounts on 9 different Git forges.
I agree, and do think it is a matter of developer education. Most professional software engineers are familiar with the github/gitlab PR-based workflow. Unfortunately very few ever have occasion to use the email patch workflow unless they want to contribute to the linux kernel or something. Maybe something like this can bridge the gap but idk: https://pr.pico.sh/
Sourcehut actually has a nice website that walks you through how to send patches via e-mail with a mailing list & repository that you can experiment with. https://git-send-email.io/