{"thread":{"id":"1740","subject":"merge noise in git-shortlog output","startedAt":"2005-09-06T21:44:00Z","lastAt":"2005-09-06T22:02:21Z","messageCount":2,"participants":["Luck, Tony","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"8145","messageId":"200509062144.j86Li04N010540@agluck-lia64.sc.intel.com","threadId":"1740","inReplyTo":null,"subject":"merge noise in git-shortlog output","fromName":"Luck, Tony","fromEmail":"tony.luck@intel.com","sentAt":"2005-09-06T21:44:00Z","receivedAt":"2005-09-06T21:44:00Z","isPatch":false,"sender":{"key":"tony.luck@intel.com","avatar":"https://avatars.githubusercontent.com/u/5446021?v=4"},"body":"Looking at the shortlog information for 2.6.13 there are a lot (eleven)\nof changes attributed to me that look like:\n\n  Auto merge with /home/aegl/GIT/linus\n\nThis is valid (I really did make all those commits, they happen every\ntime I merge the \"linus\" branch into my release branch, which I like to\ndo quite often so I'm working near the bleeding edge), but it doesn't\nseem all that useful in the \"short\" log output[1]\n\nIf \"Auto merge\" isn't a good string to match for the purposes of\ntrimming, then I can make my scripts use something else.\n\n-Tony\n\n[1] unless I can persuade Intel to base my bonus on the number of\ncommits I get included into the base :-)\n"},{"id":"8147","messageId":"7vfyshg8ia.fsf@assigned-by-dhcp.cox.net","threadId":"1740","inReplyTo":"200509062144.j86Li04N010540@agluck-lia64.sc.intel.com","subject":"Re: merge noise in git-shortlog output","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-09-06T22:02:21Z","receivedAt":"2005-09-06T22:02:21Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Luck, Tony\" <tony.luck@intel.com> writes:\n\n> This is valid (I really did make all those commits, they happen every\n> time I merge the \"linus\" branch into my release branch, which I like to\n> do quite often so I'm working near the bleeding edge), but it doesn't\n> seem all that useful in the \"short\" log output[1]\n\nAre there interesting merges and uninteresting automerges?  Are\nall merges more or less uninteresting?  If merges are not\ninteresting:\n\n    $ git log --no-merges --pretty=short $rev $argu $ments | git shortlog\n"}]}