I'll test this. I'm impressed by how much code you have removed and I'm happy to put it in petsc-dev, but we're building up a lot of changes to petsc-3.3. Should we call the next patch release 3.3.1 instead of 3.3p? It's a significant enough change that people should be able to test for it with the PETSC_VERSION_ macros.
This line can certainly be removed. +#define PETSC_MAX_YAML_LEN 128000 On Fri, Aug 17, 2012 at 1:52 PM, Blaise Bourdin <bourdin at lsu.edu> wrote: > Hi, > > Here is a revised version of my YAML patch that eliminates the limit on > the yaml file length. Is there any rational objection to pushing it to > petsc-3.3 and petsc-dev? > > Blaise > > > > -- > Department of Mathematics and Center for Computation & Technology > Louisiana State University, Baton Rouge, LA 70803, USA > Tel. +1 (225) 578 1612, Fax +1 (225) 578 4276 > http://www.math.lsu.edu/~bourdin > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120817/ae46d7c5/attachment.html>
