On Nov 17, 2013, at 11:44 AM, Raphael Kubo da Costa wrote: > Raphael Kubo da Costa <[email protected]> writes: > >> Following up on the recent thread about libpng and CMake 2.8.12, I'm >> wondering what the best way to submit a few other options is. For >> example, I sent https://sourceforge.net/p/brlcad/patches/243/ a while >> ago but it seems to have gone unnoticed. Should I assign it to someone, >> or is it better to send patches to the mailing list? > > Hmm, apparently r58508 also contains the same fix in patch 243, but was > apparently done without knowing the patch existed.
Hi Raphael, The patch tracker is usually fine but the timing was unfortunate. It overlapped with our participation in GCI and all hands were quite busy. I'm still catching up from all the backlogged activity myself. By the the time the patch was looked at, as you noted, someone else had already fixed it. The fastest way for simple build patches like this is usually to share them via IRC so someone can just apply the fix quick. The tracker is good when review or discussion are warranted. Is there more? Cheers! Sean ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
