Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Learn to use email with Git

git-send-email.io

Post reply on HN
Print view View original

41–50 of 76 posts

Re: Show HN: Learn to use email with Git

#41

Post by defanor »

yellowapple wrote: post #33
bo1024 wrote: post #6

Earlier quoted context omitted.

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

Ooooooo. Is there such a thing as SSMTP/SIMAP (i.e. something that is to SMTP/IMAP as SFTP is to FTP - i.e. an SSH-based thing that sends and/or receives mail to/from a mail server)? It'd be badass to be able to literally just use my SSH keys to authenticate when sending/receiving mail.

I'm using a setup similar to the described one, though without SMTP or IMAP: a MUA is set to use `ssh sendmail` instead of a local sendmail, and `doveadm sync sh -c ... "ssh doveadm dsync-server"` for retrieval/synchronization. It's indeed nice and handy.

Edit: My setup with mu4e is described in more detail at https://defanor.uberspace.net/notes/email.xhtml

Re: Show HN: Learn to use email with Git

#43

Post by ddevault »

bo1024 wrote: post #40
Sir_Cmpwn wrote: post #8

Earlier quoted context omitted.

>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:…

Thanks for the reply. I'll explain why I'm still confused/unsure what is going on, hope it is useful feedback. My understanding of git is that there is a server, and users push/pull to the server. So from an initial look at everything you provided, it sounded to me like git-send-email gives people email notifications to know what has been changed on the server, for example. I don't know what "email-driven workflow" m…

That's right. git stores all of the data that could be on the server on your local machine. Every clone of a git repository contains the full history of that repo. git send-email allows you to send commits to other people over email.

Re: Show HN: Learn to use email with Git

#44

Post by thristian »

jancsika wrote: post #36
stronglikedan wrote: post #13

Earlier quoted context omitted.

IMHO, the single-most underused HTML attribute. I get annoyed when I have to aim for the tiny box, instead of the nice long string of text next to it. Although, I can't count the number of times I was guilty of omitting it many moons ago.

Isn't it better to nest the checkbox inside the label? Then you don't need the for attribute nor an id.

That works nicely for checkboxes, but sometimes you want the form field and label to be in (say) different cells of a table row or something.

Re: Show HN: Learn to use email with Git

#45

Post by chmln »

saagarjha wrote: post #39
chmln wrote: post #32

This is great for small one-off projects, but I don't know why anyone would want to promote the usage of mailing lists in general. The industry moved on to more centralized solutions like github for a reason - mailing lists are clunky, intuitive, and simply horrible for large discussions. Because old and large projects are using them doesn't mean it's a good reason for new projects to use them today. If anyone has pr…

> mailing lists are clunky, intuitive, and simply horrible for large discussions On the contrary, I largely prefer mailing lists for non-code discussions (i.e. things that are not code review or filing bugs). When Swift's mailing lists moved to Discourse I realized that I stopped interacting with it as much because it was more inconvenient to work with (especially on mobile).

If you self-host your own git service, you could email everyone e.g. in a specific organization very easily. On something like GitHub it's nearly impossible, but when you own your data its just a database query + email away.

Re: Show HN: Learn to use email with Git

#46

Post by rgoulter »

bo1024 wrote: post #40
Sir_Cmpwn wrote: post #8

Earlier quoted context omitted.

>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:…

Thanks for the reply. I'll explain why I'm still confused/unsure what is going on, hope it is useful feedback. My understanding of git is that there is a server, and users push/pull to the server. So from an initial look at everything you provided, it sounded to me like git-send-email gives people email notifications to know what has been changed on the server, for example. I don't know what "email-driven workflow" m…

> My understanding of git is that there is a server, and users push/pull to the server.

Git is a distributed VCS and so doesn't need a (centralised) server to share code.

Sites like GitHub, GitLab or SourceHut let you host a git repository that you can push/pull from. It's a convenient way of sharing code, and collaborating with others.

But you can also apply changes to a repo using patches prepared by email.

> ....where there is no server at all and pushes and pulls are communicated completely via email.

I'd emphasise that changes to a repo can come from diffs or patches as well, not just pushes/pulls from another repository.

FWIW, Git book has details about how one might make use of patches received by email. https://git-scm.com/book/en/v2/Distributed-Git-Maintaining-a... https://git-scm.com/book/en/v2/Appendix-C%3A-Git-Commands-Em...

Re: Show HN: Learn to use email with Git

#47

Post by bo1024 »

ddevault wrote: post #43
bo1024 wrote: post #40

Earlier quoted context omitted.

Thanks for the reply. I'll explain why I'm still confused/unsure what is going on, hope it is useful feedback. My understanding of git is that there is a server, and users push/pull to the server. So from an initial look at everything you provided, it sounded to me like git-send-email gives people email notifications to know what has been changed on the server, for example. I don't know what "email-driven workflow" m…

That's right. git stores all of the data that could be on the server on your local machine. Every clone of a git repository contains the full history of that repo. git send-email allows you to send commits to other people over email.

Okay, thanks! I am finally getting it.

Re: Show HN: Learn to use email with Git

#48

Post by jalbertbowden »

rhn_mk1 wrote: post #14
OJFord wrote: post #2

No JS - I was baffled - did not know about ` ">`. Nice. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/la...

It seems to have a cost though, how do I link to a specific page? Anti-snark edit: what's the URL to a specific step?

? https://git-send-email.io/#step-2

Re: Show HN: Learn to use email with Git

#49

Post by jalbertbowden »

jancsika wrote: post #36
stronglikedan wrote: post #13

Earlier quoted context omitted.

IMHO, the single-most underused HTML attribute. I get annoyed when I have to aim for the tiny box, instead of the nice long string of text next to it. Although, I can't count the number of times I was guilty of omitting it many moons ago.

Isn't it better to nest the checkbox inside the label? Then you don't need the for attribute nor an id.

labels should always be to the right of the checkbox/radio controls. never nest them. nesting is ok for other form controls in some instances, but you'll run into issues with various screen readers if you apply the for attribute while nesting. on that note, always nest when possible; the ux benefits make it crazy not to take advantage of it.
Post reply on HN