On Sat, Feb 5, 2011 at 2:09 AM, Caolán McNamara <span dir="ltr"><<a href="mailto:caolanm@redhat.com">caolanm@redhat.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <div class="im">On Fri, 2011-02-04 at 09:44 +0000, Michael Meeks wrote:<br> > Caolan - are you happy for this:<br> > commit 6c01edfe66d6e350b20178d9ab367806d956cb46<br> > Author: Caolán McNamara <<a href="mailto:caolanm@redhat.com">caolanm@redhat.com</a>><br> > Date: Thu Nov 11 13:31:33 2010 +0000<br> > Resolves: #i25247#, #i25561#, #i48064#, #i92341# CTL/Other Default<br> > Font<br> > to go to libreoffice-3-3 ? if so, I guess that's fine without further<br> > review; at least it looks like an Oracle patch to me - 'ftcAsci' eg. ;-)<br> </div>Its my patch, so I'm happy with it by definition, and someone else<br> probably needs to do a quick review of it. "ftcAsci" is the spelling<br> used in the MS docs for this (IIRC), not mine.<br></blockquote><div><br>The intention for my original post is two fold:-<br>1) I'd like to know when/which-version will this fix land in.<br>2) I'd like to understand the policy for development vs. release branches. For example, which committed patches will be in the 3.3.1 or 3.4 release. How things like this are planned/decided (which used to be group by child workspaces before).<br> </div></div><br clear="all"><br>-- <br>_/|\_ Samphan Raruenrom. Open Source Development Co., Ltd.<br>Tel: +66 38 311816, Fax: +66 38 773128, <a href="http://www.osdev.co.th/">http://www.osdev.co.th/</a><br>