On May 24, 2011, at 2:41 PM, Nicola Pero wrote: > This patch fixes libobjc/48177. I applied it to trunk. > > I'd like to apply this patch to the 4.6 branch too. Do I need permission > from > a Release Manager ?
They are always welcome to chime in, though, in this case the libobjc maintainer can approve it. For hard to get wrong things that kill desirable features in obscure corners, such a change is fine. If you wanted to make substantive changes to the register allocator to get 0.001% better on spec, well, that would not fly. You'd want to be extra careful to not break the build, even with trivial changes, as objc is built by default. Generally, we manage this by checking into trunk, and letting it bake for a week while people built it. All that said, if you break the build or create regressions, the RMs reserve the right to whack you with a dead fish. > The modern API (recommended from GCC 4.6.0 onwards) has a more limited, and > elegant, set of functions, > and the code in gnustep-base would be massively simplified ... if only this > bug wasn't in the way! :-( Fixing important bugs in the only user of the library, would be a really nice thing. > So, OK to commit to the 4.6 branch too ? Ok. :-)
