maybe i should write a blog post about how, no, you don't need to use git via email or wait for forgefed to be useable in order to use git in a decentralised manner

@SRAZKVT People seem to be horrified of git over email
I should write a blog post about how I dm people git patches and tell them the command used to apply them

@SRAZKVT tell me more!

@SRAZKVT je suis curieux de lire ça 🤔 tu penses a quoi pour faire ça ?

@rick si tu clone mon repo, fais tes changements, et push sur ton remote, je peux en local littéralement juste faire un pull / fetch de tes changements

super facile en plus, juste `git fetch <<url>> <<branchRemote>>:<<branchLocal>>` et j'ai dans <<branchLocal>>le contenu de ce que tu as dans <<branchRemote>> sur ton remote

le seul problème de ceci est de regrouper le tout, car juste avec ça y a aucun système de discussion, mais ça veut aussi dire que tu peux utiliser n'importe quel système de discussion

@usernameswift yeah but i find it cleaner to just git fetch from someone's remote than have to wrangle with email

@monsieuricon right, so you see how forges like github basically keep two seperate repos ? one for the upstream, one for the fork ? and upstream kind of just pulls from the fork ? yea well that but with the repo url instead, and you do it manually instead of forge doing it for you

does have some of the same problems such forges have, but also has benefits: i can keep the same repo to contribute both to upstream and to someone's pr, instead of needing a seperate repo for each, and also you don't need to be on same platform, as long as you can fetch the repo, you'll be able to get patches in

though it does have downsides like, like github etc, still need to have essentially duplicates on remotes, and also there's no method for discussion, but that could also be nice since you could tack it onto pretty much anything you want

frankly, it's nothing incredible, but i feel it'd be much nicer than something like github where you're pretty much locked to the same forge

@SRAZKVT my only issue with the git fetch approach (which git even can generate a mail asking someone to fetch, see `man git-request-pull`) is that it still assumes i'm hosting my changes somewhere

the neat thing about git-email for me, is i can clone, make a small patch, mail it out, i'm done. if the maintainer wants to merge it they do, if they don't want to cool, i'm not forced to hold a semi-fork hosted on my personal repos until it's merged, then remember to delete the whole fork

this isn't useful for big changes, but for small spontaneous prs, it's amazing

@navi yeah, that's absolutely something nice about email, and like, in theory, email is probably the nicest way to work with git

but idk something just feels wrong imo to use email for that, but i generally feel weird about a lot of things tbh

@SRAZKVT Merci, c'est vrai qu'il y a aussi ça que j'utilise de temps en temps, je pensais qu'il y avait une autre fonctionnalité cachée

@rick pas du tout, c'est ultra basique