Rong Bao reports that git fetch --all --depth=<SOME-DEPTH> and git fetch --all --unshallow fail to deepen the repository in Git 2.56.0.

The reproduction creates a three-commit remote, makes a --depth 1 clone of it, and then runs the multi-remote fetch. The message excerpt ends before the observed result, but the report's premise is that the history stays shallow.

The message is also a patch, titled "fetch: fix --depth= and --unshallow for multi-remote fetches". The excerpts do not show its diff or explain the root cause.

No one has replied yet, so the fix has not been reviewed.