Re: [petsc-dev] PETSc blame digest (next) 2019-06-20

2019-06-20 Thread Václav Hapla via petsc-dev
Yes, I think that's the reason we moved it to private :-) Sometimes I see _Internal. I thought _Private is preferred for static functions visible only within a single object file? Vaclav 20. června 2019 21:50:29 SELČ, "Smith, Barry F." napsal: > >It HAS A hid_t argument! Making it public

Re: [petsc-dev] PETSc blame digest (next) 2019-06-20

2019-06-20 Thread Jed Brown via petsc-dev
"Hapla Vaclav" writes: >> On 20 Jun 2019, at 15:56, Vaclav Hapla wrote: >> >> >> >>> On 20 Jun 2019, at 15:52, Vaclav Hapla wrote: >>> >>> >>> On 20 Jun 2019, at 15:15, Hapla Vaclav wrote: > On 20 Jun 2019, at 15:14, Jed Brown wrote: > > Hapla

Re: [petsc-dev] PETSc blame digest (next) 2019-06-20

2019-06-20 Thread Hapla Vaclav via petsc-dev
> On 20 Jun 2019, at 15:56, Vaclav Hapla wrote: > > > >> On 20 Jun 2019, at 15:52, Vaclav Hapla wrote: >> >> >> >>> On 20 Jun 2019, at 15:15, Hapla Vaclav wrote: >>> >>> >>> On 20 Jun 2019, at 15:14, Jed Brown wrote: Hapla Vaclav via petsc-dev writes: >>

Re: [petsc-dev] PETSc blame digest (next) 2019-06-20

2019-06-20 Thread Jed Brown via petsc-dev
Hapla Vaclav via petsc-dev writes: >> On 20 Jun 2019, at 14:28, PETSc checkBuilds >> wrote: >> >> >> >> Dear PETSc developer, >> >> This email contains listings of contributions attributed to you by >> `git blame` that caused compiler errors or warnings in PETSc automated >> testing.

Re: [petsc-dev] PETSc blame digest (next) 2019-06-20

2019-06-20 Thread Hapla Vaclav via petsc-dev
> On 20 Jun 2019, at 14:28, PETSc checkBuilds > wrote: > > > > Dear PETSc developer, > > This email contains listings of contributions attributed to you by > `git blame` that caused compiler errors or warnings in PETSc automated > testing. Follow the links to see the full log files.