threads / discuss / 1740

merge noise in git-shortlog output

Subject: merge noise in git-shortlog output

## tl;dr

2 messages between Sep 6, 2005 and Sep 6, 2005.

replies: 1people: 2as markdown or json

Luck, Tony· Sep 6, 2005, 21:44 UTC · lore

Looking at the shortlog information for 2.6.13 there are a lot (eleven) of changes attributed to me that look like:

  Auto merge with /home/aegl/GIT/linus

This is valid (I really did make all those commits, they happen every time I merge the "linus" branch into my release branch, which I like to do quite often so I'm working near the bleeding edge), but it doesn't seem all that useful in the "short" log output[1]

If "Auto merge" isn't a good string to match for the purposes of trimming, then I can make my scripts use something else.

-Tony

[1] unless I can persuade Intel to base my bonus on the number of commits I get included into the base :-)

Junio C Hamano· Sep 6, 2005, 22:02 UTC · re: Luck, Tony · lore

Re: merge noise in git-shortlog output

"Luck, Tony" <tony.luck@intel.com> writes:

> This is valid (I really did make all those commits, they happen every
> time I merge the "linus" branch into my release branch, which I like to
> do quite often so I'm working near the bleeding edge), but it doesn't
> seem all that useful in the "short" log output[1]

Are there interesting merges and uninteresting automerges? Are all merges more or less uninteresting? If merges are not interesting:

    $ git log --no-merges --pretty=short $rev $argu $ments | git shortlog