On 30.07.20 11:16, Nobuhiro Iwamatsu wrote:
-----Original Message-----Not all, I sometime checked and updated this.
From: Chris Paterson [mailto:Chris.Paterson2@renesas.com]
Sent: Thursday, July 23, 2020 6:37 PM
To: email@example.com; iwamatsu nobuhiro(岩松 信洋 □ＳＷＣ◯ＡＣＴ)
<firstname.lastname@example.org>; email@example.com; firstname.lastname@example.org; SZ.Lin@moxa.com; email@example.com
Subject: CIP Patchwork
CIP has a Patchwork instance  that monitors the cip-dev mainline list for patches.
It doesn't look like it's particularly maintained, with most patches in the "new" state.
As a project, do we want to start maintaining Patchwork? Should we kill it off? Or just stick with the status-quo?
We briefly discussed this in the IRC meeting today, but I thought we should check with a wider audience before making
There are more non-kernel patches, so I re-check this.
And I use this for patch tracking and patch appling.
Can we set filters based on common tags like "[isar-cip-core]" (which I just forgot to use)?
So, any thoughts?
Kind regards, Chris
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux