Why is git send-email so awful in 2017? https://blog.flameeyes.eu/2017/07/why-is-git-send-email-so-awful-in-2017/?utm_source=newsblur&utm_campaign=ifttt&utm_medium=social … via @NewsBlur
-
-
Replying to @flameeyes @NewsBlur
git format-patch + minor postprocessing + whatever email program you like.
1 reply 0 retweets 0 likes -
But the sendmail command line interface (the interface, not the awful historic sw) has nothing serious wrong with it.
1 reply 0 retweets 0 likes -
Replying to @RichFelker @NewsBlur
It does, it's intended as a system level interface rather than being desktop oriented.
1 reply 0 retweets 0 likes -
Replying to @flameeyes @NewsBlur
I don't follow/don't understand how there's anything "system level" about the interface.
1 reply 0 retweets 0 likes -
Replying to @RichFelker @NewsBlur
It's clunky to implement locally. Not saying it's impossible, just clunky.
1 reply 0 retweets 0 likes -
Replying to @flameeyes @NewsBlur
I view it like autoconf - awful implementation(s) but the externally facing interface is fine except possibly minor cosmetic issues.
1 reply 0 retweets 0 likes -
FWIW the reason I found git send-email awful was completely different: no way to stage, check/edit, and save a copy before sending.
1 reply 0 retweets 1 like
Also the box I was working on had no email-sending access. Needed to be able to xfer to somewhere privileged to send.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.