> > $ 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-

> > $ 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".