Nicholas Clark wrote: > Applied to blead as 1487aac67a72b9f87b24113f65b4d878401bee33
Thanks. > I then re-applied the changes from > http://rt.perl.org/rt3/Public/Bug/Display.html?id=61492 > to blead as 2f30d0d0af5b459d5c0f4734d92d4b55e9dcc9b7 as it seemed to be a fix > for a class of build failure: Oh good, that grotty compiler check has been nothing but trouble. I'll apply it. > I *didn't* re-apply the part of 4954abf77fcbac122d63699b1b3921b4d44d4570 to > blead: *snip* > as I think it was this part: > > This also silences an odd warning from MM_Any.pm that comes up once in a > while, which I believe is to do with a deeper core failure as it occurs in > code utterly unrelated to these changes. Yeah, I saw that one and decided not to integrate. I prefer *not* to silence warnings until I understand what caused them. So if you see that warning again, let me know so I can diagnose. > The docs still say: > > Send patches and ideas to C<makemaker@perl.org>. > > should I be raising RT tickets for these instead? Keep raising RT tickets. That's just there for simplicity. Speaking of core coordination, now that we're on git I've been pondering how best to take advantage of that. Because this sort of thing above happens a lot. I'm going to experiment with somehow working with a fork of perl rather than my own repository. I've made a fork on github, do you guys take github pull requests? -- Reality is that which, when you stop believing in it, doesn't go away. -- Phillip K. Dick
