Message206074
| Author |
RubyTuesdayDONO |
| Recipients |
RubyTuesdayDONO, dmalcolm, gregory.p.smith |
| Date |
2013年12月13日.13:19:17 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAA-SZJGaEfkBywHGdgcOSgqZzc+fMSBR=DFEnFC=knxOXbP7Wg@mail.gmail.com> |
| In-reply-to |
<1386444925.92.0.761499023098.issue19901@psf.upfronthosting.co.za> |
| Content |
On Sat, Dec 7, 2013 at 1:35 PM, Gregory P. Smith <report@bugs.python.org>
wrote:
> I fixed this in 3.3 and 3.4 several weeks ago.
Sorry for the duplicate message a few moments ago ... "fat-fingered" my send
button.
So, has the fix just not reached the Portage tree yet? I don't fully
understand how upstream commits reach Portage, and would appreciate any
direction you might have to avoid reporting something already fixed. |
|