<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 02 Feb 2012, at 09:06, Blaise Thorn wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; ">On 02.02.2012 1:46, Blaise Thorn wrote:<br><br><blockquote type="cite">For know, I am here for a different request: I reckon that small fixes, especially those not directly related to closures, ought to be submitted separately.<br></blockquote><br>Or I could create something like<span class="Apple-converted-space"> </span><a href="http://svn.freepascal.org/svn/fpc/branches/blaise/misc">http://svn.freepascal.org/svn/fpc/branches/blaise/misc</a><span class="Apple-converted-space"> </span>and ask for its periodical reintegration into the trunk. The only tricky part with SVN, as I understand, is to "reopen" such branch after every reintegration.<br></span></span></blockquote></div><br><div>The easiest way for us would be if you could file a bug report for every independent patch (with a test program). Your proposed misc branch is also possible, but in that case make sure to also add test programs when fixing things. Re-syncing it with trunk after merging should be no problem as long as nobody changes the indentation of your patches or so.</div><div><br></div><div><br></div><div>Jonas</div></body></html>