The Disconnected Git Workflow

29 points by ploum


vimpostor

Nice! I use the same setup, except I automatically empty the msmtp queue with the same periodic timer that syncs my mail, populates the notmuch database, and generates mutt aliases for autocompleting all contacts present in the inbox, that way I don't have to think about outgoing mails when I go online again.

Being able to contribute completely offline has been a life saver quite a few times. I can't help but roll my eyes when people pretend that mail-based workflows are clumsy. The onetime setup cost of git send-email is minimal thanks to sendmailcmd like the article mentions, after that the workflow is the same for every project.

The PR workflow is way more ridiculous, where it's always the same three unnecessary steps of first create a fork, don't forget to not commit on the main branch, then open PR on Web or CLI. And embarassingly the Github review UI is still an UX nightmare. And of course it doesn't work offline.

toastal

This workflow scales to non-Git VCSs too

makishimu

How do you keep copies of mail sent this way (for the record)? In particular, when you mail a list and it doesn't send a copy back.