Barry Smith <bsm...@mcs.anl.gov> writes: > This could be extended a bit by the gitcommit value in moab.py > which means don't use moab master by default. But I think this > could be dangerous to ever use since there is only one value, it is > not per branch of PETSc-dev,
It would be perverted to try to keep the branch mapping in the file, but petsc-branch:moab.py could name a commit on a MOAB branch, possibly updated on merge. > so better to keep the simple model of petsc master uses moab > master. This means that MOAB merging an API change would break PETSc 'master', unless it was synchronized with PETSc merging a matching branch. I think this is undesirable.
pgpyW5Wd2HVSp.pgp
Description: PGP signature
