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. 😍
@prologic@twtxt.net so sending to main will include your diff from the branch feature?
@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?
@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 @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! ;-)
@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?
@prologic@twtxt.net Nice going there!
