On 2022-09-02 at 19:27:55, Lana Deere wrote: > I'm testing an upgrade to git 2.37.2 from the current version we're > using of 2.18.0. When I try to pull in my development tree, 2.37.2 > gives me an error but 2.18.0 things all is fine: > > $ /tools/linux-x86_64/git/2.37.2/bin/git pull > Your configuration specifies to merge with the ref > 'refs/heads/feature/switch-to-qt5' > from the remote, but no such ref was fetched. > > $ /tools/linux-x86_64/git/2.18.0/bin/git pull > From http://githost:7990/scm/dp/sw > * branch feature/switch-to-qt5 -> FETCH_HEAD > Already up to date. > > Anyone have any ideas about this? All I could find on google was a > suggestion that the "no such ref" message indicates the remote branch > was deleted, but that's not the case here. Can you provide the output of `git ls-remote origin` (assuming that's the remote you're using) and `git config -l` (the latter with both versions)? I don't know of any reason why Git 2.37 should be broken in this regard, but I suspect that there's a difference in configuration between the two leading to this. -- brian m. carlson (he/him or they/them) Toronto, Ontario, CA
Attachment:
signature.asc
Description: PGP signature
