4 ms·

> $ git send-email --to=<mailing list> <commit range to send> > > That was hard. So how the hell does that work? Like, how does git know how to send e-mail?

> $ git send-email --to=<mailing list> <commit range to send> > > That was hard. So how the hell does that work? Like, how does git know how to send e-mail? Do I have to stick smtp creds in somewhere? > I find this hard to believe. You've never hand-edited a diff file with `git add -p` or `git checkout -p` -- or even done a `git diff`, `git show` or `git log -p`? I did all of the above things just today, let alone in the past three years... There are many, many ways to interact with git, such as the many, many tools that make it so you don't have to interact with all that shit. tortoisegit is a wonderful tool, and it makes git SO much nicer. > But chronological order isn't what you want for ML threads. You want to read it as a tree, because that's how people use email... Patch review isn't like a YouTube comment thread. Except generally, before I'd interact with a ML, I want to see what the ML is like, and having to click through many, many pages with little content on each is just dumb. Also, you may use e-mail as a tree, but that's you. I use thunderbird, and you can set it to display as a tree, or you can set it to not, and I personally don't. As far as I can tell, 99% of the ML content I've read is basically a shitty, shitty implementation of a simple forum on a much crapper transport.

orangeshark 10y ago
You can add send-email configuration in your .gitconfig. Here is an example from the documentation that uses gmail. https://git-scm.com/docs/git-send-email#_use_gmail_as_the_smtp_server https://git-scm.com/docs/git-send-email#_use_gmail_as_the_sm...
toomuchtodo 10y ago
> As far as I can tell, 99% of the ML content I've read is basically a shitty, shitty implementation of a simple forum on a much crapper transport. And when Github goes belly up, or whatever the SaaS version control flavor of the month is, mailing lists and their archives will still be there. Simplicity is the ultimate sophistication.
- orf 10y ago
  And they will still be shit, until it's too hard to find anyone to collaborate on your projects.
  - deleted 10y ago
    [deleted]
cyphar 10y ago
> > $ git send-email --to=<mailing list> <commit range to send> > > That was hard. > So how the hell does that work? > Like, how does git know how to send e-mail? Do I have to stick smtp creds in somewhere? git send-email implements SMTP. You can give it your credentials directly using git config, or by using sendmail which quite a few people have set up (I use esmtp which is an implementation of sendmail that is very simplistic and just requires a password, server and username). And it all "just works". > As far as I can tell, 99% of the ML content I've read is basically a shitty, shitty implementation of a simple forum on a much crapper transport. Except forums are shit if you want to have different discussions about four somewhat-related patches. How do you handle trees of discussion like that? > Also, you may use e-mail as a tree, but that's you. I use thunderbird, and you can set it to display as a tree, or you can set it to not, and I personally don't. I don't use it as a tree when answering normal emails, but if you're Cc'd to three different discussions in the same thread it's much nicer to be able to see WTF the person above was responding to with better granularity than "something said on this mailing list at some point in the past".
- notriddle 10y ago
  > Except forums are shit if you want to have different discussions about four somewhat-related patches. How do you handle trees of discussion like that? You're literally typing this into a forum that supports that kind of tree of discussion, and you're literally having a side-conversation right now. A web forum can implement any style of conversation you can conceive; the web's very generic that way. I think GitHub deliberately doesn't support that kind of thing because they want to encourage having lots of little issues instead of a few big ones. It does get annoying for pull requests, though...

orangeshark 10y ago

You can add send-email configuration in your .gitconfig. Here is an example from the documentation that uses gmail. https://git-scm.com/docs/git-send-email#_use_gmail_as_the_smtp_server https://git-scm.com/docs/git-send-email#_use_gmail_as_the_sm...

toomuchtodo 10y ago

> As far as I can tell, 99% of the ML content I've read is basically a shitty, shitty implementation of a simple forum on a much crapper transport. And when Github goes belly up, or whatever the SaaS version control flavor of the month is, mailing lists and their archives will still be there. Simplicity is the ultimate sophistication.

orf 10y ago
And they will still be shit, until it's too hard to find anyone to collaborate on your projects.
- deleted 10y ago
  [deleted]

cyphar 10y ago

> > $ git send-email --to=<mailing list> <commit range to send> > > That was hard. > So how the hell does that work? > Like, how does git know how to send e-mail? Do I have to stick smtp creds in somewhere? git send-email implements SMTP. You can give it your credentials directly using git config, or by using sendmail which quite a few people have set up (I use esmtp which is an implementation of sendmail that is very simplistic and just requires a password, server and username). And it all "just works". > As far as I can tell, 99% of the ML content I've read is basically a shitty, shitty implementation of a simple forum on a much crapper transport. Except forums are shit if you want to have different discussions about four somewhat-related patches. How do you handle trees of discussion like that? > Also, you may use e-mail as a tree, but that's you. I use thunderbird, and you can set it to display as a tree, or you can set it to not, and I personally don't. I don't use it as a tree when answering normal emails, but if you're Cc'd to three different discussions in the same thread it's much nicer to be able to see WTF the person above was responding to with better granularity than "something said on this mailing list at some point in the past".

notriddle 10y ago
> Except forums are shit if you want to have different discussions about four somewhat-related patches. How do you handle trees of discussion like that? You're literally typing this into a forum that supports that kind of tree of discussion, and you're literally having a side-conversation right now. A web forum can implement any style of conversation you can conceive; the web's very generic that way. I think GitHub deliberately doesn't support that kind of thing because they want to encourage having lots of little issues instead of a few big ones. It does get annoying for pull requests, though...