From: Pavel Machek <pavel@denx.de>
To: cip-dev@lists.cip-project.org
Cc: uli@fpond.eu
Subject: Re: [cip-dev] Coordinating stable reviews
Date: Mon, 27 Sep 2021 12:17:28 +0200 [thread overview]
Message-ID: <20210927101728.GB11971@amd> (raw)
In-Reply-To: <16A8A6032C9B7813.26412@lists.cip-project.org>
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
Hi!
> 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?
I guess I should mention alternate possibilities. We could try to
somehow "hash" the commits... Perhaps I'd review all the patches where
upstream sha begins with 0-6. But patches in -stable often come in
series that depend on each other, and it would be good if single
person reviewed them.
We could also split based on first character of subject, or on
subsystem patch touches. I guess that would have other disadvantages
like uneven distribution of work when big ammount of btrfs fixes hits
the -stable.
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: cip-dev@lists.cip-project.org
Cc: uli@fpond.eu
Subject: Re: [cip-dev] Coordinating stable reviews
Date: Mon, 27 Sep 2021 12:17:28 +0200 [thread overview]
Message-ID: <20210927101728.GB11971@amd> (raw)
Message-ID: <20210927101728.iRtCBSNHkIeC7xljzISh7Vcxy0o0T6ZNYji9S5uFKtQ@z> (raw)
In-Reply-To: <16A8A6032C9B7813.26412@lists.cip-project.org>
[-- Attachment #1.1: Type: text/plain, Size: 964 bytes --]
Hi!
> 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?
I guess I should mention alternate possibilities. We could try to
somehow "hash" the commits... Perhaps I'd review all the patches where
upstream sha begins with 0-6. But patches in -stable often come in
series that depend on each other, and it would be good if single
person reviewed them.
We could also split based on first character of subject, or on
subsystem patch touches. I guess that would have other disadvantages
like uneven distribution of work when big ammount of btrfs fixes hits
the -stable.
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 (#6752): https://lists.cip-project.org/g/cip-dev/message/6752
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 parent reply other threads:[~2021-09-27 10:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16A8A6032C9B7813.26412@lists.cip-project.org>
2021-09-27 10:17 ` Pavel Machek [this message]
2021-09-27 10:17 ` [cip-dev] Coordinating stable reviews Pavel Machek
2021-09-27 10:09 Pavel Machek
2021-09-27 10:09 ` [cip-dev] " 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=20210927101728.GB11971@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox