git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: merge noise in git-shortlog output

From
Junio C Hamano <junkio@cox.net>
Date
Sep 6, 2005, 22:02 UTC
Message-ID
<7vfyshg8ia.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<200509062144.j86Li04N010540@agluck-lia64.sc.intel.com>
"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
Previous: Luck, Tony
Message 2 of 2 in “merge noise in git-shortlog output”
  1. Luck, TonySep 6, 2005
  2. Junio C HamanoSep 6, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.