<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<blockquote cite="mid:20120503100749.082383F492@toad.stack.nl"
type="cite">
<pre wrap="">
Policy wise, I merge revisions for utils, packages and the higher level
units of RTL like sysutils and classes if they are a couple of weeks old
(3-4 weeks), but I usually leave big changes a bit longer.
</pre>
</blockquote>
ok it is answer to my question ;-)<br>
So we can expect backporting after approx. month<br>
<br>
<blockquote cite="mid:20120503100749.082383F492@toad.stack.nl"
type="cite">
<pre wrap="">
Since last weekend there is a notes system that allows me to add notes to
the revs in mergelogs. See r21037 on the database page, it has a red "notes"
attached to it. Clicking it will unfold it.
</pre>
</blockquote>
yes I noticed it ;-)<br>
<br>
Please add also red comment to <b>21009</b> that this revision DO NOT
backport (it is "only" test), because I used there array constructor,
which AFAIK is not implemented in 2.6 (so it will fail to compile)<br>
<br>
<blockquote cite="mid:20120503100749.082383F492@toad.stack.nl"
type="cite">
<pre wrap="">At a certain point you have to start considering risks vs benefits of
merging something.
</pre>
</blockquote>
Yes<br>
<br>
Thanks for deep explanation.<br>
-Laco.<br>
<br>
<blockquote cite="mid:20120503100749.082383F492@toad.stack.nl"
type="cite">
<pre wrap="">_______________________________________________
fpc-devel maillist - <a class="moz-txt-link-abbreviated" href="mailto:fpc-devel@lists.freepascal.org">fpc-devel@lists.freepascal.org</a>
<a class="moz-txt-link-freetext" href="http://lists.freepascal.org/mailman/listinfo/fpc-devel">http://lists.freepascal.org/mailman/listinfo/fpc-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>