<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-15"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
No, it is a bad idea. But it was only afterwards that I found out<br>
that 2.0.1 is in yet another branch. I'll revert the patch in a second.<br>
<br>
Oliver<br>
<br>
Am 2010-05-28 16:45, schrieb Jö Fahlke:
<blockquote cite="mid:20100528144523.GJ31407@paranoia" type="cite">
<pre wrap="">Am Fri, 28. May 2010, 16:23:45 +0200 schrieb <a class="moz-txt-link-abbreviated" href="mailto:sander@dune-project.org:">sander@dune-project.org:</a>
</pre>
<blockquote type="cite">
<pre wrap="">Author: sander
Date: 2010-05-28 16:23:45 +0200 (Fri, 28 May 2010)
New Revision: 6720
Modified:
releases/2.0/dune/grid/common/gridfactory.hh
Log:
patches 6718-6719 (add missing methods/implementations in the default factory) merged from the trunk
</pre>
</blockquote>
<pre wrap="">
Is it really a good idea to modify the release branch after the release has
been made? If you want to prepare for a bugfix release, I suggest creating a
branch 2.0.1 or 2.1 or similar by copying from the 2.0 branch.
Jö.
</pre>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Dune mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Dune@dune-project.org">Dune@dune-project.org</a>
<a class="moz-txt-link-freetext" href="http://lists.dune-project.org/mailman/listinfo/dune">http://lists.dune-project.org/mailman/listinfo/dune</a>
</pre>
</blockquote>
<br>
</body>
</html>