> I'm also subscribed to a mailing list for the computer vision library I > used during my PhD which also uses git and has a summary format: > http://lists.nongnu.org/archive/html/libcvd-members/2011-10/msg00014.html > > That's quite a nice format just for keeping on top of what's happening. Sure, but that's not what the commit list is about, at least not on that level. While a summary of the 'oneline' option at the top would be nice, having a least the abbreviated diffs (as before) would be tremendously helpful -- I know that I only rarely read diffs past the point where its commit message is cut off due to laziness and lack of time, and I'm sure I'm not alone there. Furthermore, I find the format used there rather bad -- the same kind of information could be presented a lot easier. > I thought of suggesting a separate mailing list haiku-commits-summary > with that format, but I also don't want to miss out on the interesting > discussions which sometimes follow a particular commit, so I'm not sure > what the best answer is. For that, an RSS feed is indeed better suited. I think the best possible solution was already suggested by Ingo. Or, alternatively, one message for each commit with a numbering so that you know which commits belong together (like "1/8"). Bye, Axel.