From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] about patch review process
Date: Thu, 14 Mar 2019 11:02:14 +0100 [thread overview]
Message-ID: <4324304.6oKhBapyEa@linux-3zh6> (raw)
In-Reply-To: <CAGDrK-ZwHwo3f0Zakf34N+QJ+vk=z6bLebwgrjVzZHsv40UKgg@mail.gmail.com>
Hi,
On jueves, 14 de marzo de 2019 5:35:54 (CET) Nobuhiro Iwamatsu wrote:
> Hi, all.
>
> The kernel team is reviewing the stable tree patch that is the basis
> of the CIP kernel.
> The review results are managed on the wiki[0], but they have not been
> updated often.
> The kernel team discussed the issue in IRC and considered a simple process.
>
> I created a template with a tool[1] to create these wiki pages and
> v4.4.176[2] patch list.
> The review process considers the following:
>
> 1. A new LTS will be released.
> 2. Create a list on wiki.
> 3. Mark the review and the name of the worker and mark (UR: under
> review) under the commit.
> 4. When the review is over, update the mark.
> 5. Work report on IRC.
>
> I would like to make the review active based on these. This list is
> also maintained in the git repository[1].
> These are classical andalso suggestions. If you have an opinion,
> please let me know.
I think it would be easier to use the Gitlab wiki if you want to automate the
process since it has git in the backend and you can orchestrate the process
through pipelines. Then I would point to the specific gitlab wiki page in the
LF wiki.
>
> Best regards,
> Nobuhiro
>
> [0]:
> https://wiki.linuxfoundation.org/civilinfrastructureplatform/linux-4.4.y
> [1]: https://gitlab.com/cip-project/cip-kernel/lts-commit-list
> [2]:
> https://wiki.linuxfoundation.org/civilinfrastructureplatform/review-linux-4
> .4.176 _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev
--
Agust?n Benito Bethencourt
Principal Consultant
Codethink Ltd
We respect your privacy. See https://www.codethink.co.uk/privacy.html
next prev parent reply other threads:[~2019-03-14 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 4:35 [cip-dev] about patch review process Nobuhiro Iwamatsu
2019-03-14 10:02 ` Agustin Benito Bethencourt [this message]
2019-03-17 23:07 ` Nobuhiro Iwamatsu
2019-03-28 9:55 ` Nobuhiro Iwamatsu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4324304.6oKhBapyEa@linux-3zh6 \
--to=agustin.benito@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox