[petsc-dev] moab nightlybuild failure

[Jed Brown]

Satish Balay <balay at mcs.anl.gov> writes:

> With such extra metadata - one could potentially do such tarcking of
> updates with tarballs aswell.

For that, you'd have to have positive identification for a tarball
version (perhaps its SHA1) and keep the association with the working
tree.

> But for what Barry wants - we need subrepo type support where we keep track of
> snapshot relations at each step of progress of petsc-dev  & moab-dev.
>
> As it stands now - if you checkout petsc-dev from a few weeks back [or
> working on a branch for that long] - you get latest moab that could
> potentially have conflicts.

That is the reason for 'gitcommit' referring to a specific commit.
-------------- 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/b3d9b069/attachment.sig>