Closed ezkl closed 5 years ago
thanks for the report; I can confirm this. The commit indeed looks like a probable culprit.
I sent a mail to the git@ list.
Link to git issue/thread https://public-inbox.org/git/CAFQ2z_O7rupGS4rntiUwJCHUj3bO0U88bVAToveEo_uU0Eu96w@mail.gmail.com/
Setting
remote.origin.fetch
to+refs/heads/*:refs/heads/*
during the clone ingitindex.CloneRepo()
results in an error with git v2.21.0 (released recently.)The most straightforward way I was able to reproduce was to install both versions of git (v2.21.0 and v2.20.1) and
git clone
directly:I was able to reproduce on both macOS 10.12 and Ubuntu 16.04. A superficial scan of recent changes to git makes me think that https://github.com/git/git/commit/515be8338237c1f0f98ff826ba98f50d1dff5517 may be the change that introduced the problem, but I haven't verified.