Earlier quoted context omitted.
How is that harder than signing up to Github?
I think you meant “how is signing up for GitHub harder than that?”
Oops yes.
Email and Git = <3
251–260 of 265 posts
Re: Email and Git = <3
#252Earlier quoted context omitted.
How is that harder than signing up to Github?
I only have to sign up to Github once, not once per project.
That’s because Microsoft GitHub is a proprietary monolith. Compare that to the open core & self-hosting of GitLab the more FOSS-positive space where each server (without federation) requires a new sign up, confirmation emails (meaning you already had to go thru email), CAPTCHAs, setting up new keys, etc. That said, you will need to get your email filters in place or you can get a lot of new, unwanted mail (assuming you are required to sign up which often isn’t the case).
Re: Email and Git = <3
#253Not really a huge fan of this whole method, but the GitHub CLI is really well thought out and means I basically never need to leave the terminal if I don't want to.
How will that CLI work when using non-proprietary Git (or other VCS) servers? Sounds like a way to get stuck in walled garden.
Re: Email and Git = <3
#254Too bad google has disabled "insecure apps" meaning I have a couple of ffmpeg patches sitting around because I haven't yet migrated it to my own domain. I thinking of sending from "FuckYouGoogle".
If this caused more folks to jump ship away from letting Google read all of their messages (as well as mine from the other end), then I’m all for it.
Re: Email and Git = <3
#255This is so absurd. The complexity of this setup is off the charts. If you thought memorizing terrible inconsistent git commands was bad enough, this just cranks it to 11
Re: Email and Git = <3
#256Not really a huge fan of this whole method, but the GitHub CLI is really well thought out and means I basically never need to leave the terminal if I don't want to.
> but the GitHub CLI is really well thought
How do you get to that conclusion?
Re: Email and Git = <3
#257Not really a huge fan of this whole method, but the GitHub CLI is really well thought out and means I basically never need to leave the terminal if I don't want to.
> but the GitHub CLI is really well thought How do you get to that conclusion? https://stevelosh.com/blog/2013/04/git-koans/
The GitHub CLI is a completely different tool than the git CLI
Re: Email and Git = <3
#258Re: Email and Git = <3
#259I appreciate the effort here, but after learning the workflow and having to get all this set up on a few computers, having to configure git send-mail is honestly just needlessly annoying and absurd. Organizations that insist on using workflows like git send-mail and mailing lists not only drive away a significant number of potential contributors, but they also form a weirdly religious culture that fetishizes needless…
I personally self host git and think that email gives a bunch of advantages:
1. Email has clients with full offline support. Sometimes I work in locations where internet is bad to nonexistent and with github I am limited in what I can do.
2. Anyone can contribute to my repos without needing to sign up to my website. Git with email truly allows decentralization of “forges”. So in the same vain, I can contribute with the same client to any project on the web that accepts email patches and it’s the same workflow for all of them.
3. Since I have an email client for my email, I can set up my own custom workflow that is much faster. Github siloes you into a begrudgingly slow one. My email client integrates into my editor and gives me the same keyboard shortcuts I use to navigate my code.
4. Did I mention it removes centralization? Having github be the center for all repos makes it ripe for enshittification. Given Microsoft’s history for EEE, I don’t trust them one bit.
Re: Email and Git = <3
#260I appreciate the effort here, but after learning the workflow and having to get all this set up on a few computers, having to configure git send-mail is honestly just needlessly annoying and absurd. Organizations that insist on using workflows like git send-mail and mailing lists not only drive away a significant number of potential contributors, but they also form a weirdly religious culture that fetishizes needless…
It's easy to forget the maintainers' side of this. Yes, most contributors will prefer opening a PR on GitHub as apposed to mailinglists. But imagine instead that you are David Miller, and it's your job to consume the absolute fire hose of patches and messages related to Linux's networking subsystem. Would you rather wade through the hundreds of messages and patches coming in every day using either GitHub PRs and issu…
It’s easier for contributors too, you don’t need an account.