Stefan Krah wrote: > Antoine Pitrou <solipsis at pitrou.net> wrote: >>> For instance I have several one line patches languishing, I can't imagine >>> how disappointing it would be to have significantly larger patches ignored, >>> but it happens. >> Can you give a pointer to these one-liners? > > Almost a one-liner, but vast knowledge required (how do you prove that > using (freefunc) is safe if it's the first usage in the tree?). > > http://bugs.python.org/file21610/atexit-leak.patch > But how do you find issues? I want to do some reviews, but I don't want to wade through issues on components I know little or nothing about in order to find the ones I can review. There does not seem to be a way to filter search results in the tracker. Cheers, Mark
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4