Hello Guilherme, On Tue, 17 Jan 2012 15:44:02 -0300 Guilherme Salgado <guilherme.salg...@linaro.org> wrote:
[] > > So, based on all this, I wouldn't think there's something to > > patch-track: it's not that much of upstream contribution, more of > > upstream bugreport + local workaround. But if you think we could > > track anything out of this, I'd appreciate a hint how to start with > > that. > > Right, it probably doesn't make sense to teach patches.l.o how to > suck patches submitted by Linaro engineers from issues.jenkins-ci.org > as we don't expect to see many contributions from Linaro there. If > that changes in the future, we can certainly work something out, like > we did for gerrit. > > The way you described it sounds like the patch you submitted isn't > even going to be merged upstream, but if you have others that you > expect to be, you can just email a copy of them to patches@l.o, as > described at That's my patch was just commenting some code around. I now tested (tracked as https://bugs.launchpad.net/linaro-android-infrastructure/+bug/917704), the latest changes to the plugin made by the maintainer, and they were re-done properly: using conditionals driven by UI configuration settings. > > https://wiki.linaro.org/Process/UpstreamPatches > > In that case you'll also want to ask for the creation of a new > project on patches.l.o (instructions also on the page above) Sounds good, thanks! -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
