<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Oct 28, 2013 at 9:34 AM, Beman Dawes <span dir="ltr"><<a href="mailto:bdawes@acm.org" target="_blank">bdawes@acm.org</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><div class="h5">On Mon, Oct 28, 2013 at 8:35 AM, Tom Kent <span dir="ltr"><<a href="mailto:lists@teeks99.com" target="_blank">lists@teeks99.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div dir="ltr"><div><div><div class="gmail_extra">...<br></div></div></div><div class="gmail_extra">That worked great for trunk, but now the problem appears to have spread to release...could we get the fix applied there as well?<br> </div></div></blockquote> <div><br></div></div></div><div> Argh! I merged 86392 and 86398 yesterday but forgot to check if Steven's 86426 had been merged.<br><br></div><div>I'll apply for permission to merge right away.<br></div></div></div> </div></blockquote></div><br></div><div class="gmail_extra">OK, 86503 merged 86426 from trunk to release. Should be OK now,<br><br></div><div class="gmail_extra">Thanks,<br><br></div><div class="gmail_extra">--Beman<br></div> </div>