<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">On 2nd thought, if there’s interest in creating a 2.7.1 bug-fix release ASAP, this can definitely wait...<div class=""><div class=""><br class=""><div><br class=""><div class=""></div></div><blockquote type="cite" class=""><div><div class="">On 2021-05-25-T, at 13:13, Christopher Nielsen <<a href="mailto:mascguy@rochester.rr.com" class="">mascguy@rochester.rr.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><span class=""><span class=""><div class="">Josh, is there any interest in adding base PR 242, which fixes double-space messages for ‘port diagnose’?</div><div class=""><br class=""></div><div class=""><a href="https://github.com/macports/macports-base/pull/242" class="">https://github.com/macports/macports-base/pull/242</a></div><div class=""><br class=""></div></span></span><div class=""><br class=""></div><div class=""><div class=""></div><blockquote type="cite" class=""><div class="">On May 25, 2021, at 11:29:32, Joshua Root wrote:</div><div class=""><br class=""></div><div class="">Any objection to tagging the current state of the release-2.7 branch as 2.7.1?</div></blockquote></div></div></div></div></div></blockquote></div></div></body></html>