From: Johannes Sixt <J.Sixt@eudaptics.com>
To: git@vger.kernel.org
Subject: git-rev-list: --objects list inconsistency
Date: Tue, 14 Nov 2006 16:54:17 +0100 [thread overview]
Message-ID: <4559E6A9.9A30A236@eudaptics.com> (raw)
I observed a puzzling behavior of git-rev-list:
$ git-rev-list master^^..master
f3364ca9405e17772fecea1d06c40b9965b8e6e4
bb3bfda219a85d2d49e62c261b9c8f6795ebdc22
$ git-rev-list --max-count=2 master
f3364ca9405e17772fecea1d06c40b9965b8e6e4
bb3bfda219a85d2d49e62c261b9c8f6795ebdc22
$ git-rev-list --objects master^^..master |wc -l
10
$ git-rev-list --objects --max-count=2 master |wc -l
2376
As you can see, without --objects, master^^..master and --max-count=2
list the same two commits.
But with --objects I get different object lists. I don't even know which
one is the one to expect, but I certainly would not have expected the
lists to be different. What's wrong here?
BTW, the objects listed with --objects --max-count=2 are basically the
entire tree at master plus the few objects that changed since master^^.
$ git --version
git version 1.4.4.rc2.gc8641
-- Hannes
next reply other threads:[~2006-11-14 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 15:54 Johannes Sixt [this message]
2006-11-14 17:58 ` git-rev-list: --objects list inconsistency Junio C Hamano
2006-11-14 18:26 ` Linus Torvalds
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=4559E6A9.9A30A236@eudaptics.com \
--to=j.sixt@eudaptics.com \
--cc=git@vger.kernel.org \
/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).