[OE-core] [Openembedded-architecture] Patchwork & patch handling improvements
Barros Pena, Belen
belen.barros.pena at intel.com
Thu Dec 3 11:43:29 UTC 2015
On 02/12/2015 18:43, "Burton, Ross" <ross.burton at intel.com> wrote:
>
>On 2 December 2015 at 18:04, Martin Jansa
><martin.jansa at gmail.com> wrote:
>
>I'm depending on bundles heavily, to "mark" the patches for layers with
>dedicated maintainer and also for extra "status" like merged in
>"master-next" branch for jenkins build, because standard status values
>aren't fine-grained enough.
>
>
>
>
>Sounds like instead of bundles the new patchworks needs the ability for a
>single list to represent multiple projects (so there'd be a meta-oe,
>meta-python, etc),
That's already in place
https://github.com/dlespiau/patchwork/issues/15
>and more status values.
You can add status values (to the db directly or via the Django admin
interface), but they will apply to all projects in the Patchwork instance.
Ideally you should be able to set a list of status values per project I
guess.
Cheers
Belén
>
>
>Ross
>
More information about the Openembedded-core
mailing list