<div dir="ltr">On Mon, Mar 11, 2013 at 3:35 PM, Karl Rupp <span dir="ltr"><<a href="mailto:rupp@mcs.anl.gov" target="_blank">rupp@mcs.anl.gov</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">Hi Sean,<br>
<br>
>>> Satish, please remove me from petsc-maint. Also, remove me from the<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
developers webpage. I have already purged petsc-dev from my system and<br>
won't be pushing anything else from now on.<br>
</blockquote>
<br>
Huh, why this? This is not forced change of religion...<br>
</blockquote>
<br>
Why should I bother? Everyone will listen to Jed anyway. Sorry about the<br>
CUDA+cmake patches, by the way, those are gone now.<br>
</blockquote>
<br></div></div>
it will still be possible to work with Mercurial. The need for a new/better development model was also based on stability issues repeatedly raised by users at SIAM CSE, as you certainly remember.<br></blockquote><div><br>
</div><div style>My characterization of it is more that we adopted a particular piece of technology because we thought</div><div style>it was better architected and might in the future promise efficiency gains. I don't think this will be any</div>
<div style>more stable than everyone working in different clones for different projects. The technology here is</div><div style>lightweight branches, which is supposed to deliver efficiencies not available to the multiple clone model.</div>
<div style>We will see :)</div><div style><br></div><div style> Matt</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The decision followed a technical evaluation of the workflow, not on a<br>
'Sean vs. Jed'-type of personal preference. Thus, you really should not take this personal.<br>
<br>
Best regards,<br>
Karli<br>
<br>
</blockquote></div><br><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>