[petsc-dev] broken nightlybuilds (next vs next-tmp)

[Satish Balay]

PETSc integrator group,

next builds have been broken for the past few weeks - preventing graduation of potentially clean branches to maint/master.

So I've switched nightlybuilds from next to next-tmp to test fewer branches at a time [and hopefully graduate them].

Tonights builds are with:

$ git fetch -p && comm -12 <(git branch -r --merged origin/next-tmp | sort) <(git branch -r --no-merged origin/master | sort)
  origin/balay/fix-mkl-batch-error/maint
  origin/barry/fix-lto_library-option-maint
  origin/barry/fix-matmult-seqdense-cherrypick/maint
  origin/stefano_zampini/cherrypick-commits-for-maint-from-continuousadjoint
<snip>

i.e branches destined for 'maint'.

Please do *not* merge any of the (other) branches currently in next to master (if you see clean next/next-tmp builds tomorrow)! 

Thanks,
Satish