Johannes Sixt [off-list ref] writes:
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^^.