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

Re: git-rev-list: --objects list inconsistency

From
Junio C Hamano <junkio@cox.net>
Date
Nov 14, 2006, 17:58 UTC
Message-ID
<7vlkmdzz9v.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<4559E6A9.9A30A236@eudaptics.com>
Johannes Sixt <J.Sixt@eudaptics.com> writes:
Show 10 quoted lines
> 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

You are asking to get objects reachable from master but exclude objects reachable from master^^.

> $ git-rev-list --objects --max-count=2 master |wc -l
>    2376
You are asking to get objects reachable from master and master^.

You have 2300+ objects that are common in trees of master, master^ and master^^.

Previous: Johannes SixtNext: Linus Torvalds
Message 2 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.