An update: Looks like we have to do the following in our existing clones: git remote set-head origin -a Satish ----- balay@sb /home/balay/petsc (main=) $ git gc fatal: bad object refs/remotes/origin/HEAD fatal: failed to run repack balay@sb /home/balay/petsc (main=) $ cat .git/refs/remotes/origin/HEAD ref: refs/remotes/origin/master balay@sb /home/balay/petsc (main=) $ git remote set-head origin -a origin/HEAD set to main balay@sb /home/balay/petsc (main=) $ cat .git/refs/remotes/origin/HEAD ref: refs/remotes/origin/main balay@sb /home/balay/petsc (main=) $ git gc --prune=now Enumerating objects: 942787, done. Counting objects: 100% (942787/942787), done. Delta compression using up to 4 threads Compressing objects: 100% (213109/213109), done. Writing objects: 100% (942787/942787), done. Total 942787 (delta 725291), reused 942001 (delta 724664), pack-reused 0 Checking connectivity: 942787, done. Expanding reachable commits in commit graph: 86669, done. balay@sb /home/balay/petsc (main=) $ On Fri, 26 Feb 2021, Satish Balay via petsc-users wrote:

Update:

the switch (at gitlab.com/petsc/petsc) is done.

Please delete your local copy of 'master' branch and start using 'main' branch.

Satish

On Tue, 23 Feb 2021, Satish Balay via petsc-dev wrote:

...

All,

This is a heads-up, we are to switch the default branch in petsc git repo from 'master' to 'main'

[Will plan to do the switch on friday the 26th]

We've previously switched 'maint' branch to 'release' before 3.14 release - and this change (to 'main') is the next step in this direction.

Satish