Hi Jim, (I'm CCing linaro-dev@ because I figure others might have similar questions)
This is because the android patches are going to the 'Unknown' project[1], which is ignored when generating the statistics[2]. We currently can't automatically detect the correct project for such patches because they are all sent to linaro-dev@ instead of their own mailing list like other projects. Maybe we could try and detect the correct project from the subject's prefix (e.g. [android/bionic]), but even then I suspect these patches are not really going to AOSP, in which case they wouldn't be included in the statistics either (much like the gcc-linaro and linaro-kernel projects).
If I'm mistaken we can just create android projects and move the patches from the Unknown project to them. A thread I started recently (Subject: Please help us setup patches.linaro.org) on linaro-dev@ has more information on how to do that.
[1] http://patches.linaro.org/patchwork/project/other-unknown/list/?state=* [2] http://patches.linaro.org/faq
Cheers,
On Wed, 2011-06-22 at 18:22 +0800, Jim Huang wrote:
hi Guilherme,
I just checked the stat of Patches from the "Linaro Android Team" team: http://patches.linaro.org/team/linaro-android/
I am quite confused about the number. I did submit patches to linaro-dev and Cc. to patches@linaro.org and you can find out the recent merged patches here: (Recently closed) https://review.source.android.com//#dashboard,1002471
Is there any problem for stat? Or, can I help to improve it?
Thanks, -jserv
On Wed, Jun 22, 2011 at 1:51 PM, Guilherme Salgado guilherme.salgado@linaro.org wrote:
Hi Jim, (I'm CCing linaro-dev@ because I figure others might have similar questions)
This is because the android patches are going to the 'Unknown' project[1], which is ignored when generating the statistics[2]. We currently can't automatically detect the correct project for such patches because they are all sent to linaro-dev@ instead of their own mailing list like other projects. Maybe we could try and detect the correct project from the subject's prefix (e.g. [android/bionic]), but even then I suspect these patches are not really going to AOSP, in which case they wouldn't be included in the statistics either (much like the gcc-linaro and linaro-kernel projects).
If I'm mistaken we can just create android projects and move the patches from the Unknown project to them. A thread I started recently (Subject: Please help us setup patches.linaro.org) on linaro-dev@ has more information on how to do that.
I thought we had worked out a special way how to ensure that patches that go to upstream gerrit get considered? Or was that just discussion that we still have to finish?
On Thu, 23 Jun 2011 14:25:18 +0200, Alexander Sack asac@linaro.org wrote:
I thought we had worked out a special way how to ensure that patches that go to upstream gerrit get considered? Or was that just discussion that we still have to finish?
No, we didn't agree to complete something like that at this time and so didn't implement anything.
Thanks,
James
Lets sort this out for 11.07. Got a meeting scheduled:
Tracking AOSP upstream pick up in patches.linaro.org
BP:
https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-track-a...
On 23 June 2011 08:01, James Westby james.westby@canonical.com wrote:
On Thu, 23 Jun 2011 14:25:18 +0200, Alexander Sack asac@linaro.org wrote:
I thought we had worked out a special way how to ensure that patches that go to upstream gerrit get considered? Or was that just discussion that we still have to finish?
No, we didn't agree to complete something like that at this time and so didn't implement anything.
Thanks,
James
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev