[petsc-dev] 'master' RESET after bad merge! - 'tisaac/thplex' was based on 'next'

Matthew Knepley knepley at gmail.com
Thu Sep 4 11:33:58 CDT 2014

On Thu, Sep 4, 2014 at 11:28 AM, Jed Brown <jed at jedbrown.org> wrote:

> Matthew Knepley <knepley at gmail.com> writes:
> > It seems that I am talking to myself, but I will say it again. People
> > miss things, especially in routine setting where it gets
> > repetitive. Having automated checks and warnings is very helpful:
> Reviewing commits before merging is the integrator's raison d'être.
> If your job was an airplane inspector, would it be important to automate
> checking whether there is a bear in the cockpit?  It's pretty dangerous
> to fly the plane when there is a bear in the cockpit and if you just
> sign the form without checking, some poor pilot is going to get in that
> cockpit with a steak sandwich and nothing good can come of that.  But if
> you actually go in the cockpit to inspect the instruments, it's going to
> be hard to miss the bear.

It is important to check things that do happen. If bears do wander in the
and are not noticed for some time, then this would be important to automate.


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/20140904/03b904ba/attachment.html>

More information about the petsc-dev mailing list