On 2022-09-06 15:37:45-0400, Lana Deere <lana.deere@xxxxxxxxx> wrote: > This is the final output from git bisect: > > $ git bisect good > Bisecting: 0 revisions left to test after this (roughly 0 steps) > [d8d3d632f4165955da49032d50279c20cfbde2e5] hooks--update.sample: use > hash-agnostic zero OID > > Does that offer any hint about what is going on? It is still bisecting, can you continue to bisect until it says something like: first bad commit is ... > > Incidentally, some but not all of the pulls produced additional > output. Maybe it's a clue? > > $ ~/tmp/git/install/bin/git pull > warning: Pulling without specifying how to reconcile divergent branches is > discouraged. You can squelch this message by running one of the following > commands sometime before your next pull: > > git config pull.rebase false # merge (the default strategy) > git config pull.rebase true # rebase > git config pull.ff only # fast-forward only > > You can replace "git config" with "git config --global" to set a default > preference for all repositories. You can also pass --rebase, --no-rebase, > or --ff-only on the command line to override the configured default per > invocation. This is a hint in some version of git for 2 modes of pull, you can ignore it. -- Danh
