All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: uli@fpond.eu, cip-dev@lists.cip-project.org
Subject: Coordinating stable reviews
Date: Mon, 27 Sep 2021 12:09:50 +0200	[thread overview]
Message-ID: <20210927100950.GA11971@amd> (raw)

[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]

Hi!

It is good to review "stable" patches soon, because such reviews are
more useful for the stable community, and because when bug is spotted,
it is easier to get patch dropped in the 5.10.X-rc phase than waiting
for 5.10.X release and then having patch reverted in 5.10.X+1.

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?

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: "Pavel Machek" <pavel@denx.de>
To: uli@fpond.eu, cip-dev@lists.cip-project.org
Subject: [cip-dev] Coordinating stable reviews
Date: Mon, 27 Sep 2021 12:09:50 +0200	[thread overview]
Message-ID: <20210927100950.GA11971@amd> (raw)
Message-ID: <20210927100950.XADjhsAymfeV3gfxkSNzvNuzpKm3KIHeJZN_XIveD5Q@z> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1221 bytes --]

Hi!

It is good to review "stable" patches soon, because such reviews are
more useful for the stable community, and because when bug is spotted,
it is easier to get patch dropped in the 5.10.X-rc phase than waiting
for 5.10.X release and then having patch reverted in 5.10.X+1.

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?

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 429 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6751): https://lists.cip-project.org/g/cip-dev/message/6751
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]
-=-=-=-=-=-=-=-=-=-=-=-


             reply	other threads:[~2021-09-27 10:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27 10:09 Pavel Machek [this message]
2021-09-27 10:09 ` [cip-dev] Coordinating stable reviews Pavel Machek
2021-09-27 10:43 ` Ulrich Hecht
2021-09-27 10:43   ` Ulrich Hecht
2021-09-28 12:29 ` nobuhiro1.iwamatsu
2021-09-28 12:29   ` 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=20210927100950.GA11971@amd \
    --to=pavel@denx.de \
    --cc=cip-dev@lists.cip-project.org \
    --cc=uli@fpond.eu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.