[petsc-dev] [PETSc checkBuilds] PETSc blame digest (next) 2015-08-24

Matthew Knepley knepley at gmail.com
Mon Aug 24 14:14:27 CDT 2015


On Mon, Aug 24, 2015 at 11:53 AM, Jed Brown <jed at jedbrown.org> wrote:

> Matthew Knepley <knepley at gmail.com> writes:
> > It does not understand part of the toolchain, so I do not even think its
> > crappy in this instance :)
>
> Well, it's not about not understanding the toolchain.  If someone
> changes an API, but does not update all call sites, the person that
> wrote the original call site (perhaps years ago) gets blamed.  I don't
> know an easy way to do better except to bisect the history (somewhat
> expensive because builds and tests are not very fast).
>

Oh, this is different I think. The /*@C was accidentally removed so a
Fortran
interface leaked through that should not have.

  Matt

-- 
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20150824/7d310845/attachment.html>


More information about the petsc-dev mailing list