<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Jun 6, 2014 at 12:33 PM, Jed Brown <span dir="ltr"><<a href="mailto:jed@jedbrown.org" target="_blank">jed@jedbrown.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">Matthew Knepley <<a href="mailto:knepley@gmail.com">knepley@gmail.com</a>> writes:<br>
<br>
> On Thu, Jun 5, 2014 at 8:37 AM, Barry Smith <<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>> wrote:<br>
><br>
>><br>
>> We’ll be making a PETSc release in a few days so please get anything<br>
>> you need into next for testing and movement over to master.<br>
>><br>
><br>
> I want knepley/feature-problem-class and knepley/fix-fe-gpu in. They are<br>
> pushed to 'next; for tonight, and can be in master tomorrow. I<br>
> expect no problems.<br>
<br>
</div>How do we note that these interfaces are not stable and will likely<br>
change soon after the release? (At least I think the current<br>
arrangement is brittle and either will not last or will not be used<br>
much.)<br>
</blockquote></div><br>Feel free to note on the list that you think it should be done a different, as yet unspecified</div><div class="gmail_extra">or coded, way.</div><div class="gmail_extra"><br></div><div class="gmail_extra">
Matt<br clear="all"><div><br></div>-- <br>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>-- Norbert Wiener
</div></div>