From: A Large Angry SCM <gitzilla@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [BUG] git-log shows first parent and repeated last for octopus merge
Date: Wed, 18 Oct 2006 09:35:32 -0700 [thread overview]
Message-ID: <453657D4.70502@gmail.com> (raw)
In-Reply-To: <eh5242$rar$1@sea.gmane.org>
Jakub Narebski wrote:
> When trying to find how many merges and how many octopus merges (merges with
> more than two parents) are in git.git repository I have encountered the
> following strange output of git-log:
Maybe the following will find what you're looking for:
git-rev-list master --parents \
|sed -e 's/[0-9a-f]\{40\}//' -e 's/ [0-9a-f]\{40\}/*/g' \
|sort \
|uniq -c
prev parent reply other threads:[~2006-10-18 16:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 11:11 [BUG] git-log shows first parent and repeated last for octopus merge Jakub Narebski
2006-10-18 13:53 ` Johannes Schindelin
2006-10-18 14:02 ` Jakub Narebski
2006-10-18 14:26 ` [PATCH] When rewriting parents, cull duplicates Johannes Schindelin
2006-10-18 19:02 ` [BUG] git-log shows first parent and repeated last for octopus merge Junio C Hamano
2006-10-18 16:35 ` A Large Angry SCM [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=453657D4.70502@gmail.com \
--to=gitzilla@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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.
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 NNTP newsgroup(s).