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

git-rev-list: --objects list inconsistency

From
Johannes Sixt <j.sixt@eudaptics.com>
Date
Nov 14, 2006, 15:54 UTC
Message-ID
<4559E6A9.9A30A236@eudaptics.com>
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: Junio C Hamano
Message 1 of 3 in “git-rev-list: --objects list inconsistency”
  1. Johannes SixtNov 14, 2006
  2. Junio C HamanoNov 14, 2006
  3. Linus TorvaldsNov 14, 2006

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.