Liu Yubao wrote: > Junio C Hamano wrote: >> [...] It is also a bad >> example because I can answer that question with this command >> line: >> >> git log --grep='^Merge .* into next$' next >> >> and while it is a perfectly valid answer, I know it would leave >> you feeling somewhat cheated. >> > smart trick, but if the logs aren't consistent enough it's hard to > grep them out. Well, commit message for merges are generated automatically. And if you set merge.summary=true in repo config (or your config), then you have shortlog in merge commit message by default... -- Jakub Narebski Warsaw, Poland ShadeHawk on #git - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html