All (next users), ref: https://lists.mcs.anl.gov/pipermail/petsc-dev/2017-September/021361.html
I've recreated 'next' branch - and have a backup for current 'next' at 'next-apr-2018'. So if you have/use 'next' branch in your clone - please do the following (in all your git clones): git checkout master git fetch git branch -D next git checkout next Please *do not push* from a stale 'next' branch in your clone. If this is attempted, the merge step should get a *conflict* on include/petscversion.h. i.e this merge conflict indicates you have to recreate next - and *not* resolve/push. $ git fetch $ git merge origin/next Auto-merging include/petscversion.h CONFLICT (content): Merge conflict in include/petscversion.h Automatic merge failed; fix conflicts and then commit the result. Satish ------ Ref:currently merged branches in old next $ comm -12 <(git branch -r --merged origin/next-apr-2018 | sort) <(git branch -r --no-merged origin/master | sort) origin/knepley/fix-dm-gmg origin/knepley/fix-ex62-tests origin/knepley/fix-fe-bd-integral origin/knepley/fix-fe-vector-spaces origin/knepley/fix-snes-ex69 origin/tisaac/feature-dmfield
