[sfink]

It's not people intimidated by email. It's people intimidated by configuring their system to programmatically send email.

Residential ISPs, for example, usually block smtp ports. You can send via gmail, but that still requires some fiddly configuration. And at least the way I figured out how to do it, it involves a cleartext password sitting on my filesystem, which I'm not too happy about. (It's a password limited to sending email as me, but that's kind of a big deal.)

I would much prefer to push patches to people's projects via my revision control system. It's ok with me if that requires some sort of push-only account.

[u801e]

> And at least the way I figured out how to do it, it involves a cleartext password sitting on my filesystem

git credential allows for programs to query it for credentials based on the server you're connecting to and store it for a configurable period of time in memory. So you don't have to store your password in the config file. You would enter it on the command line when you invoke git send-email and if you run the same command within the configured time period, you won't have to re-enter your password.