Re: 2.37.2 can't "git pull" but 2.18.0 can

On Wed, Sep 07, 2022 at 11:56:27AM -0400, Lana Deere wrote:

Sorry, I was confused by the "0 left".  With one more besect it says

9f489ac6bbb755fa4c83289e44cad12f3b765d69 is the first bad commit

That appears to be
 [9f489ac6bbb755fa4c83289e44cad12f3b765d69] Merge branch 'dl/zero-oid-in-hooks'

That seems unlikely to be the real culprit. I wonder if something went
wrong during the bisect.

A common gotcha when building Git from source is to directly run:

  /path/to/git-clone/git pull

Under the hood git-pull will run git-fetch, which it will look for in
the installed libexec dir. But of course if you didn't run "make
install", then what is there may be some old version installed
previously. Instead, you want to run:

  /path/to/git-clone/bin-wrappers/git pull

which will set up the environment so that we'll find any other git
commands inside the build directory.

That's all a wild guess, of course, but if you think that might be the
problem it's worth trying the bisect again.

-Peff