git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: git@vger.kernel.org
Subject: Re: merge noise in git-shortlog output
Date: Tue, 06 Sep 2005 15:02:21 -0700	[thread overview]
Message-ID: <7vfyshg8ia.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200509062144.j86Li04N010540@agluck-lia64.sc.intel.com> (Tony Luck's message of "Tue, 6 Sep 2005 14:44:00 -0700")

"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

      reply	other threads:[~2005-09-06 22:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-06 21:44 merge noise in git-shortlog output Luck, Tony
2005-09-06 22:02 ` Junio C Hamano [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vfyshg8ia.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=tony.luck@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).