Barry Smith <bsm...@mcs.anl.gov> writes: > BTW: it may be that petsc master and petsc next have different > gitcommit?
Yes, that's entirely okay. > I guess this would be ok, the petsc branch would have have the > gitcommit in it related to the appropriate moab.py master so when > it is merged to next and then master, next and master will get the > right new value. But this does mean we need a manual 3a) > > 3a) when the moab branch is merged into moab master the petsc branch > value of gitcommit in moab.py must be set to the new commit value of > moab master. Yes, this is the step that makes --download-moab automatically find the correct version.
pgpZdVPaHAaJX.pgp
Description: PGP signature
