Live data from Hacker News

Show HN: Learn to use email with Git

git-send-email.io

1–10 of 76 posts

Re: Show HN: Learn to use email with Git

#4
One thing a lot of email providers (at least gmail and fastmail) do is let you create application passwords that you can use for specific purposes. So if you're at all queasy about having your password in plain text on the hard drive, you can create a special password just for git.

Edit: you don't have to set up a terminal email client at this point, but if you figure out how to use git-send-email, you're just inches away from using mutt.

Re: Show HN: Learn to use email with Git

#5
post #4

One thing a lot of email providers (at least gmail and fastmail) do is let you create application passwords that you can use for specific purposes. So if you're at all queasy about having your password in plain text on the hard drive, you can create a special password just for git. Edit: you don't have to set up a terminal email client at this point, but if you figure out how to use git-send-email, you're just inches…

You can also omit it and type it in each time you use git send-email, or you can set it up with your on-site keyring using git-credential:

https://git-scm.com/docs/gitcredentials

Re: Show HN: Learn to use email with Git

#6
post #4

One thing a lot of email providers (at least gmail and fastmail) do is let you create application passwords that you can use for specific purposes. So if you're at all queasy about having your password in plain text on the hard drive, you can create a special password just for git. Edit: you don't have to set up a terminal email client at this point, but if you figure out how to use git-send-email, you're just inches…

They're getting closer to public-key authentication, I guess that's good.

Re: Show HN: Learn to use email with Git

#7
Can only speak for myself, but I didn't understand enough context to get much out of the site. I'm used git for small, personal collaborations, so I don't know why it sends email or when you would want it to do that. I don't know what a "patch" means here and why you use email with them.

If I'm not your target audience, then that's fine, but it might be helpful to have some background on this.

Otherwise, the site and layout look great to me. It is a little tricky to have step 1 be installation, because someone who just wants to find out more without installing might stop there (I was a little deterred, then I just picked a random OS and clicked through the instructions).

Re: Show HN: Learn to use email with Git

#8
post #7

Can only speak for myself, but I didn't understand enough context to get much out of the site. I'm used git for small, personal collaborations, so I don't know why it sends email or when you would want it to do that. I don't know what a "patch" means here and why you use email with them. If I'm not your target audience, then that's fine, but it might be helpful to have some background on this. Otherwise, the site and…

>I'm used git for small, personal collaborations

This is a great reason to use email! You don't need a platform at all, you can use the tools presented in this tutorial to email your work directly to your collaborators.

Outside of that, email is used for collaboration with many large and important projects, such as Linux, PostgreSQL, and git itself. I have some writings about why I think this workflow is nice:

https://drewdevault.com/2018/07/23/Git-is-already-distribute...

https://drewdevault.com/2018/07/02/Email-driven-git.html

(forgive the formatting on the latter, fix is being deployed now)

Re: Show HN: Learn to use email with Git

#9
post #4

One thing a lot of email providers (at least gmail and fastmail) do is let you create application passwords that you can use for specific purposes. So if you're at all queasy about having your password in plain text on the hard drive, you can create a special password just for git. Edit: you don't have to set up a terminal email client at this point, but if you figure out how to use git-send-email, you're just inches…

The Google implementation of application specific passwords is horrible. There's nothing application specific about it -- it's valid for at least mail, calendar, and contacts, with no way to limit the scope. It ends up being a password that effectively bypasses all MFA on your Google account. Where do you store such a password? That's a powerful credential to be regularly unlocking.

I should be able to create a credential that's valid for just SMTP, with no IMAP or cal/card access at all.

Re: Show HN: Learn to use email with Git

#10
post #7

Can only speak for myself, but I didn't understand enough context to get much out of the site. I'm used git for small, personal collaborations, so I don't know why it sends email or when you would want it to do that. I don't know what a "patch" means here and why you use email with them. If I'm not your target audience, then that's fine, but it might be helpful to have some background on this. Otherwise, the site and…

The idea is that in order for multiple people to collaborate, most of the time you will need a service like Github, Bitbucket or perhaps something you can run yourself.

This is a different workflow. Instead of staying in sync via a hosted service, people stay in sync and send 'pull requests' via email.

Post reply on HN