💾 Archived View for log.pfad.fr › 2023 › git-send-email captured on 2024-07-08 at 23:36:22. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-11-04)
-=-=-=-=-=-=-
Git ships with built-in tools for collaborating over email. Sourcehut made a decent tutorial for it:
I was successful in following the tutorial and submitting a couple of patches. After some attempts at improving my workflow, I think I will settle on the following:
If you add three dashes (---) on a dedicated line in your commit message, everything afterward will be discarded when the patch is applied (using `git am`).
Commands after git clone:
# Check existing git config and adjust settings git config --get-regex "^format\..*" git config format.to "list@example.com" git config format.subjectprefix "PATCH project"
Commands to send the patch:
# Submit a patch git --amend # add a self-destructive message under a --- line git send-email origin/master # send the patch as email
Yes, it means that I am back to 2 commands, while still being able to resume from where I left off if anything fails.
[Attempt 2022] Git send-email with format-patch
📅 2023-05-03