[petsc-dev] http://petsc.cs.iit.edu/petsc/petsc-dev/rev/a36eb42b26ee

2012-06-07 Thread Dmitry Karpeev
When can we expect that (I mean 4.0)? Moose now rejects commits with trailing white space. Dmitry. On Thu, Jun 7, 2012 at 6:24 PM, Barry Smith wrote: > > For PETSc 4.0 we adopt an appropriate "pre-commit" source code pretty > print system; that prevents incorrectly formatted code from getting

[petsc-dev] http://petsc.cs.iit.edu/petsc/petsc-dev/rev/a36eb42b26ee

2012-06-07 Thread Barry Smith
For PETSc 4.0 we adopt an appropriate "pre-commit" source code pretty print system; that prevents incorrectly formatted code from getting into the repository. Barry On Jun 7, 2012, at 5:45 PM, Jed Brown wrote: > Did we just adopt a new line formatting convention and nobody told me? > >

[petsc-dev] http://petsc.cs.iit.edu/petsc/petsc-dev/rev/a36eb42b26ee

2012-06-07 Thread Dmitry Karpeev
If you built a nested fieldsplit and wanted to look at the ksp monitor output from all the levels of nesting, before this fix the output would be extremely confusing. This is because setting the tab level on a PCFIELDSPLIT's inner KSPs doesn't actually set the tab level on its PC. If one of those

[petsc-dev] http://petsc.cs.iit.edu/petsc/petsc-dev/rev/a36eb42b26ee

2012-06-07 Thread Jed Brown
Did we just adopt a new line formatting convention and nobody told me? ierr = PetscObjectGetOptionsPrefix((PetscObject)(ilink->ksp),&prefix); CHKERRQ(ierr); ierr = PetscObjectSetOptionsPrefix((PetscObject)(dms[i]), prefix); CHKERRQ(ierr); ierr = KSPSetDM(ilink->ks