Forks & pull requests versus emails
@sir show also discussion on the PR and how different email clients render the patch...
@sir this is brilliant. If I want to publish my long-lived branch/fork/proposed changes how would I do it? (In the GitHub model I've already done that in order to propose the change.)
@andybalaam push your branch to any git host you like
@sir but you do need to have one to push to.
@sir I like the email workflow, it's much more usable.
BTW: Do you know any sourcehut-like application but easy to self-host that is focused on few users?
With the email approach there's no need to have the huge complexity of forks, prs, and all that stuff that Gitea handles. So it would be nice to have a simple but yet useful self-hosting option. Ideas?
In my opinion Sourcehut is good, but it's not easy to self-host for small orgs or people as it's designed to be large (it is, right?)
@sir I'm really starting to get on board with the email workflow. Do you know of a good guide for receiving git email patches?
@sir Also, what are you using for email?
I'd love for some kind of guide on how to use a terminal-based email client in 2020.
@sir thanks for the video, good example to pass around to people. off topic question, what browser are you using?
@sir ho, actually you sound like a nice guy. :)
there is hope.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!