From: Luis Chamberlain <mcgrof@kernel.org>
To: linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org
Cc: patches@lists.linux.dev, amir73il@gmail.com, pankydev8@gmail.com,
tytso@mit.edu, josef@toxicpanda.com, jmeneghi@redhat.com,
jake@lwn.net, mcgrof@kernel.org
Subject: [PATCH 4/4] kdevops: make linux-kdevops the default tree
Date: Fri, 13 May 2022 12:38:31 -0700 [thread overview]
Message-ID: <20220513193831.4136212-5-mcgrof@kernel.org> (raw)
In-Reply-To: <20220513193831.4136212-1-mcgrof@kernel.org>
At LSFMM 2022 at Palm Springs it was discussed that we should
*strive* towards a shared expunge list for fstests / blktests. Although
that effort requires splitting out the expunge list from kdevops to a
new git subtree, sharing a git tree for commit work for kdevops seems
also innevitable and desirable since some of us are already
collaborating on at least one shared test runner, kdevops.
So we can start by using a shared organization for what we need
to share, we call this organization linux-kdevops [0]. This encompasses a
few usual suspects git trees which can be used by both fstests and
blktests picking a "stable" sort of git sha1sum for each and always
striving towards the latest:
* fstests
* blktests
* dbench
* ndd
We'll be using the linux-kdevops organization for what trees we use and
trust that those in the organization will communicate what is needed before
making controversial changes.
This is perhaps the first controversial change, but it only applies to
kdevops, so if you are not using kdevops as a test runner you probably
won't care.
Those using kdevops should become aware that they should change
their default upstream to use linux-kdevops URL now:
So we switch from:
https://github.com/mcgrof/kdevops
To:
https://github.com/linux-kdevops/kdevops
Users which change this on a live environemtn would also then just have
to change the CONFIG_WORKFLOW_KDEVOPS_GIT on their configuration so
they'd just run:
make menuconfig # set CONFIG_WORKFLOW_KDEVOPS_GIT to https://github.com/linux-kdevops/kdevops
make
make kdevops-git-reset
Those who have commit access to the organization linux-kdevops can
then just commit as needed to help move baselines forwards and if
and when something comes up which really seems controversial we can
use the mailing lists as with this change.
[0] https://github.com/orgs/linux-kdevops/
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---
kconfigs/workflows/Kconfig.shared | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kconfigs/workflows/Kconfig.shared b/kconfigs/workflows/Kconfig.shared
index 4cccfbe..4a2ecf6 100644
--- a/kconfigs/workflows/Kconfig.shared
+++ b/kconfigs/workflows/Kconfig.shared
@@ -47,7 +47,7 @@ endif
config WORKFLOW_KDEVOPS_GIT
string "Git tree of kdevops to clone on targets"
- default "https://github.com/mcgrof/kdevops.git" if !GIT_ALTERNATIVES && !HAVE_CUSTOM_KDEVOPS_GIT
+ default "https://github.com/linux-kdevops/kdevops.git" if !GIT_ALTERNATIVES && !HAVE_CUSTOM_KDEVOPS_GIT
default "https://github.com/linux-kdevops/kdevops.git" if GIT_LINUX_KDEVOPS_GITHUB
default "https://gitlab.com/linux-kdevops/kdevops.git" if GIT_LINUX_KDEVOPS_GITLAB
default CUSTOM_KDEVOPS_GIT if HAVE_CUSTOM_KDEVOPS_GIT
--
2.35.1
prev parent reply other threads:[~2022-05-13 19:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 19:38 [PATCH 0/4] kdevops: use linux-kdevops for the main tree Luis Chamberlain
2022-05-13 19:38 ` [PATCH 1/4] workflows/Kconfig: be consistent when enabling fstests or blktests Luis Chamberlain
2022-05-14 2:21 ` Bart Van Assche
2022-05-15 15:10 ` Luis Chamberlain
2022-05-13 19:38 ` [PATCH 2/4] kdevops: move generic kdevops variables to its own file Luis Chamberlain
2022-05-13 19:38 ` [PATCH 3/4] playbooks: add a common playbook a git reset task for kdevops Luis Chamberlain
2022-05-20 14:44 ` Pankaj Raghav
2022-05-23 17:38 ` Luis Chamberlain
2022-05-13 19:38 ` Luis Chamberlain [this message]
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=20220513193831.4136212-5-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=amir73il@gmail.com \
--cc=jake@lwn.net \
--cc=jmeneghi@redhat.com \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=pankydev8@gmail.com \
--cc=patches@lists.linux.dev \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).