[petsc-dev] moab nightlybuild failure

Jed Brown jedbrown at mcs.anl.gov
Fri Jun 28 15:09:19 CDT 2013

Barry Smith <bsmith at 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130628/c86e5b31/attachment.sig>

More information about the petsc-dev mailing list