From: Ulrich Hecht <uli@fpond.eu>
To: cip-dev@lists.cip-project.org,
Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>,
pavel@denx.de
Cc: jan.kiszka@siemens.com, masami.ichikawa@cybertrust.co.jp
Subject: Re: [cip-dev] New kernel patches review management
Date: Thu, 11 Nov 2021 10:04:21 +0100 (CET) [thread overview]
Message-ID: <1047231455.163841.1636621461970@webmail.strato.com> (raw)
In-Reply-To: <TYAPR01MB6252AE15ABA567A3301A9F4992949@TYAPR01MB6252.jpnprd01.prod.outlook.com>
> On 11/11/2021 7:29 AM Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp> wrote:
> I considered using the gitlab wiki to switch the current patch review
> management to another.
>
> The gitlab wiki can be used as a regular git repository and can be
> viewed from his browser by writing its contents in markdown.
>
> e.g. git clone git@gitlab.com:cip-project/cip-kernel/linux-cip.wiki.git
>
> It can be created using the API on the project wiki[0]. Since
> namespaces are available, we can also create hierarchies such as
> 5.10.y/v5.10.77 [1].
> The wiki page is first filled with the commit ID, then the CIP kernel
> developer writes the name after the commit they plan to review.
>
> The commit content of [1] is an example, so please let me know if you
> have any opinions about the format and others.
It would be helpful if each line would also contain the commit title.
Other than that it looks good to me.
CU
Uli
next prev parent reply other threads:[~2021-11-11 9:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 6:29 New kernel patches review management nobuhiro1.iwamatsu
2021-11-11 9:04 ` Ulrich Hecht [this message]
2021-11-18 8:15 ` [cip-dev] " nobuhiro1.iwamatsu
2021-11-17 18:09 ` Pavel Machek
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=1047231455.163841.1636621461970@webmail.strato.com \
--to=uli@fpond.eu \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@siemens.com \
--cc=masami.ichikawa@cybertrust.co.jp \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=pavel@denx.de \
/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