<br><div class="gmail_quote">2010/2/28 Stefan Behnel <span dir="ltr"><<a href="mailto:stefan_ml@behnel.de">stefan_ml@behnel.de</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I would actually encourage Florent to do the opposite: act now and prepare<br>
a patch against the latest official ET 1.2 and cET releases (or their SVN<br>
version respectively) that integrates everything that is considered safe,<br>
i.e. everything that makes cET compatible with ET and everything that seems<br>
clearly stable in ET 1.3 and does not break compatibility for existing code<br>
that uses ET 1.2. If you send that to Fredrik, I expect little opposition<br>
to making that the base for a 1.2.8 release, which can then be folded back<br>
into the stdlib.<br>
<font color="#888888"></font><br></blockquote></div><br>I exchanged some e-mails with Fredrik last week. Not sure if it will be 1.2.8 or 1.3, but now he is positive on the goals of the patch. I've commited all the changes and external fixes to a branch of the Mercurial repo owned by Fredrik. I'm expecting an answer soon.<br>
<br>Branch based on the official etree repository (Mercurial):<br><a href="http://bitbucket.org/flox/et-2009-provolone/">http://bitbucket.org/flox/et-2009-provolone/</a><br><br>Patch based on this branch:<br><a href="http://codereview.appspot.com/207048">http://codereview.appspot.com/207048</a><br>
(patch set 7 almost identical to the tip of the Mercurial repo)<br><br>-- <br>Florent<br>