[petsc-dev] TSSetRHSJacobian web page errors

Barry Smith bsmith at mcs.anl.gov
Sun Feb 8 20:24:52 CST 2015

> On Feb 8, 2015, at 8:19 PM, Matthew Knepley <knepley at gmail.com> wrote:
> On Sun, Feb 8, 2015 at 8:18 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
> > On Feb 8, 2015, at 8:08 PM, Jed Brown <jed at jedbrown.org> wrote:
> >
> > Mark Adams <mfadams at lbl.gov> writes:
> >> Bitbucket should have some sort of graphical representation of the PETSc
> >> code base and color code who "controls" which code so that we can track of
> >> this.  Like a war room sort of thing.
> >
> > No, we should use a uniform style everywhere.  I used a typedef to
> > reduce code and to normalize the documentation.  Barry decided we should
> > do it a different way, but didn't update everything.
>    Yeah, lazyness and fear of Jed's wraith stopped me from "cleaning up" the TS public API so far :-)
> >  I don't think it's
> > urgent, but we should be consistent in new code.
> I still think its a good idea to know who is on the hook for each part since it is getting big
> enough that no one practically patrols all the code anymore.

  git has tools to help see that, sadly those tools are impossible to use for us mortals.


>    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

More information about the petsc-dev mailing list