From: Ulrich Hecht <uli@fpond.eu>
To: cip-dev@lists.cip-project.org, Pavel Machek <pavel@denx.de>
Subject: Re: [cip-dev] Coordinating stable reviews
Date: Mon, 27 Sep 2021 12:43:51 +0200 (CEST) [thread overview]
Message-ID: <1532955493.576116.1632739431463@webmail.strato.com> (raw)
In-Reply-To: <20210927100950.GA11971@amd>
> On 09/27/2021 12:09 PM Pavel Machek <pavel@denx.de> wrote:
> Unfortunately, we don't have good system for coordinating reviews in
> -rc phase.
>
> There's a script (commit.py) that produces one-line-per-patch output
> suitable for review. One possibility would be to have shared place
> somewhere reviewers could tag "I'm working on these patches".
>
> I don't believe lts-commit-list.git repository is suitable for that;
> format suitable for review is different from what we have in
> lts-commit-list, and there is going to be multiple updates per day in
> busy periods.
>
> We don't really need commit messages for this. Actually, we don't
> really need to keep history, either. It would be good if system could
> be controlled from command line for easy scripting.
>
> Any ideas what kind of service could be used for this?
gitlab comes to mind. IIUC, wiki pages are part of the project, but
contained in a separate git repository.
The output of commit.py is practically markdown already; just add a
table header and some extra "|"'s, and you're good.
There will be a history, but I think that can be safely ignored.
CU
Uli
WARNING: multiple messages have this Message-ID (diff)
From: "Ulrich Hecht" <uli@fpond.eu>
To: cip-dev@lists.cip-project.org, Pavel Machek <pavel@denx.de>
Subject: Re: [cip-dev] Coordinating stable reviews
Date: Mon, 27 Sep 2021 12:43:51 +0200 (CEST) [thread overview]
Message-ID: <1532955493.576116.1632739431463@webmail.strato.com> (raw)
Message-ID: <20210927104351.-Ksk2jsVtXNNzYAFs7as0v1o8cPOJkD6B45oQ1Ou9p4@z> (raw)
In-Reply-To: <20210927100950.GA11971@amd>
[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]
> On 09/27/2021 12:09 PM Pavel Machek <pavel@denx.de> wrote:
> Unfortunately, we don't have good system for coordinating reviews in
> -rc phase.
>
> There's a script (commit.py) that produces one-line-per-patch output
> suitable for review. One possibility would be to have shared place
> somewhere reviewers could tag "I'm working on these patches".
>
> I don't believe lts-commit-list.git repository is suitable for that;
> format suitable for review is different from what we have in
> lts-commit-list, and there is going to be multiple updates per day in
> busy periods.
>
> We don't really need commit messages for this. Actually, we don't
> really need to keep history, either. It would be good if system could
> be controlled from command line for easy scripting.
>
> Any ideas what kind of service could be used for this?
gitlab comes to mind. IIUC, wiki pages are part of the project, but
contained in a separate git repository.
The output of commit.py is practically markdown already; just add a
table header and some extra "|"'s, and you're good.
There will be a history, but I think that can be safely ignored.
CU
Uli
[-- Attachment #2: Type: text/plain, Size: 429 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6753): https://lists.cip-project.org/g/cip-dev/message/6753
Mute This Topic: https://lists.cip-project.org/mt/85896746/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/10495289/4520388/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2021-09-27 10:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 10:09 Coordinating stable reviews Pavel Machek
2021-09-27 10:09 ` [cip-dev] " Pavel Machek
2021-09-27 10:43 ` Ulrich Hecht [this message]
2021-09-27 10:43 ` Ulrich Hecht
2021-09-28 12:29 ` nobuhiro1.iwamatsu
2021-09-28 12:29 ` Nobuhiro Iwamatsu
[not found] <16A8A6032C9B7813.26412@lists.cip-project.org>
2021-09-27 10:17 ` Pavel Machek
2021-09-27 10:17 ` 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=1532955493.576116.1632739431463@webmail.strato.com \
--to=uli@fpond.eu \
--cc=cip-dev@lists.cip-project.org \
--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