On Thu, Mar 10, 2016 at 9:24 PM, Barry Smith wrote:
>
> > On Mar 10, 2016, at 9:21 PM, Satish Balay wrote:
> >
> > I pused - what I thought was a clang warnings fix. But I see it broke on
> windows.
>
> Ok, no biggie, so long as it wasn't Matt who broke the build :-)
Marcia, Marcia, Marcia!
Its fixed now.
Satish
On Thu, 10 Mar 2016, Barry Smith wrote:
>
> > On Mar 10, 2016, at 9:21 PM, Satish Balay wrote:
> >
> > I pused - what I thought was a clang warnings fix. But I see it broke on
> > windows.
>
> Ok, no biggie, so long as it wasn't Matt who broke the build :-)
>
> >
>
> On Mar 10, 2016, at 9:21 PM, Satish Balay wrote:
>
> I pused - what I thought was a clang warnings fix. But I see it broke on
> windows.
Ok, no biggie, so long as it wasn't Matt who broke the build :-)
>
> Will check..
>
> Satish
>
> On Thu, 10 Mar 2016, Barry Smith wrote:
>
>>
>> H
I pused - what I thought was a clang warnings fix. But I see it broke on
windows.
Will check..
Satish
On Thu, 10 Mar 2016, Barry Smith wrote:
>
> How'ed this crap and others get into master? Suppose to be clean in next
> first
>
>
> > On Mar 10, 2016, at 9:00 PM, PETSc checkBuilds
> >
How'ed this crap and others get into master? Suppose to be clean in next first
> On Mar 10, 2016, at 9:00 PM, PETSc checkBuilds
> wrote:
>
>
>
> Dear PETSc developer,
>
> This email contains listings of contributions attributed to you by
> `git blame` that caused compiler errors or warni
