We're planning on bringing up Gerrit at UDS for tracking Android upstreaming. Perhaps it could be used for tracking GCC patches?
On Tue, Apr 19, 2011 at 4:22 PM, James Westby james.westby@linaro.org wrote:
On Wed, 13 Apr 2011 14:54:55 +1200, Michael Hope michael.hope@linaro.org wrote:
Hmm. We already do patch tracking in Linaro GCC to make sure that all patches go upstream. It's a manual process as the GCC workflow itself is very manual.
I don't want to manually update two places when a patch changes state. How can we merge these systems?
The original plan from UDS was to start from something like your system and extend it to other teams. That changed when patches@linaro.org was proposed in Dallas.
We can perhaps modify your script to create patches in patchwork rather than bugs. I fear that may be a bit simplistic for your case though? Is there a one-to-one correspondance between bugs and "patches" that are being sent upstream?
In addition, what things do you need to track about each patch? It may be that patchwork doesn't have all the fields needed to model your workflow.
Thanks,
James
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev