I see that argument about client setup too, but it's not the reason I don't prefer email, especially for something like kernel development. I think there are r

I see that argument about client setup too, but it's not the reason I don't prefer email, especially for something like kernel development. I think there are real disadvantages to the sort of queue management required of the maintainer using email that can be alleviated by a specialized tool. It also separates the communication history from the code history, which can sometimes lead to confusion about when a specific person became aware of a patch, which is often important. I'm usually against integrating too many functions, but I think GitHub does a good job of it. Basically, I prefer GitHub's approach. I'm not deeply experienced managing open source projects, though, so my opinion is not that valuable. My basic contention was with the idea that a technology can't be better unless it's an unmixed good.