From: Luis Chamberlain <mcgrof@kernel.org>
To: helpdesk@kernel.org
Cc: Luis Chamberlain <mcgrof@kernel.org>,
jlayton@kernel.org, amir73il@gmail.com, patches@lists.linux.dev,
Shyam Kumar <skachukattu@contractor.linuxfoundation.org>
Subject: Create kdevops@lists.linux.dev
Date: Wed, 16 Aug 2023 17:00:49 -0700 [thread overview]
Message-ID: <ZN1jMaKKQ3ZRwiL3@bombadil.infradead.org> (raw)
Address : kdevops@lists.linux.dev
Description: Linux kernel kdevops project
Owners : mcgrof@kernel.org, jlayton@kernel.org, amir73il@gmail.com
Allow HTML : N
Archives : Y
Reasons for the list and additional info:
kdevops [0] has picked up momentum over the years to the point we now
have a community and reviewing patches is becoming more important.
Although we are on github and gitlab and share an organization together
I just noticed 3 pull requests have gone unnoticed for a while. So I'd
prefer to just avoid web GUI pull requests and instead we deal with
patches just as we do with Linux kernel subsystems.
Luis
next reply other threads:[~2023-08-17 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 0:00 Luis Chamberlain [this message]
2023-08-17 16:52 ` Create kdevops@lists.linux.dev Shyam Kumar
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=ZN1jMaKKQ3ZRwiL3@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=amir73il@gmail.com \
--cc=helpdesk@kernel.org \
--cc=jlayton@kernel.org \
--cc=patches@lists.linux.dev \
--cc=skachukattu@contractor.linuxfoundation.org \
/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.