Learn to use email with git! – Interesting read of how to use the “Git Email” workflow for sending patches to a project 🤔 Not sure how I feel about it though 😅
@prologic@twtxt.net there’s too many steps to me.
Love the illustrations though. 😍
@justamoment@twtxt.net Technically if you setup your ~/.gitconfig “just so” the steps are really just one.
$ git co -b feature
# hack hack hack
$ git ci -m "blah bla hblah"
$ git send-email main
@prologic@twtxt.net so sending to main will include your diff from the branch feature?
@justamoment@twtxt.net No the command compares your branch and automatically formats a patch containing your changes compared to the branch you specified.
@prologic@twtxt.net Oh! So it work for entire branches, but what about merging them? How is goes from the maintainer side, does it handle the branches automatically?
@justamoment@twtxt.net From the maitainrr side you just end up having to copy the raw contents of the emails and pipe them into git am - in the right order. It’s a bit tedious 🤦♂️
@prologic@twtxt.net yeah too bothersome, but I guess it’s good if you don’t want to rely on anything else.
@justamoment@twtxt.net Yeah, not only that, but one of the “issues” I have with the whole Git+Email patch workflow in general is that you have to basically “give up” your identity, email address and personal information in some way. I find that a bit bothersome really. – I’m sure we can come up with a proper “decentralised” way of collaborating on software with git as the primary backend for revision history and patches, but hmmm 🤔
@justamoment@twtxt.net @prologic@twtxt.net tbf, format-patch numbers your patches so that you can apply them with an one liner, no matter if they’re 1 or 9999. As for identity leakage, do notice that only author patch info is present - a name (that can be a pseudonym) and an address field that can be empty. Other then that you only have the transport means, but you don’t really need to use e-mail if that is your concern, you can for eg. set up an anonymous ftp… you just need to get the formatted patches, git not having its own transport is not a limitation but the freedom to let you get patches in any way you want! ;-)
@marado@twtxt.net Yeah so @lyse@lyse.isobeef.org and I are talking on IRC right now about an idea I had about this… I realise I could use the same git patch/diff format(s) but skip the Email parts. I was even thinking of using Twtxt itself as a sort of “notification” and some kind of easy-to-use web-based push/pull system for managing the patches and applying them to your repo(s).
@prologic@twtxt.net You mean like a git log --pretty=twtxt that someone can get for every branch of every repo on your new git web interface?
@marado@twtxt.net Yeah pretty much 🤣 I kind of have this desire to reinvent Git and Software collaboration a bit 😅 Why can’t we use Twtxt for feed, notifications and communicating reviews? 😆
@prologic@twtxt.net Nice going there!
