From: Jeff Layton <jlayton@kernel.org>
To: Luis Chamberlain <mcgrof@kernel.org>,
rt@kernel.org, chandan.babu@oracle.com, amir73il@gmail.com,
josef@toxicpanda.com, a.manzanares@samsung.com
Cc: patches <patches@lists.linux.dev>
Subject: Re: Mailing list request for kdevops enable persistent disks
Date: Sat, 12 Aug 2023 08:21:43 -0400 [thread overview]
Message-ID: <0b69bd4142afc5be0a8d76d00373d93317f609c3.camel@kernel.org> (raw)
In-Reply-To: <ZMwi5oDiAKGpPh8B@bombadil.infradead.org>
On Thu, 2023-08-03 at 14:57 -0700, Luis Chamberlain wrote:
> 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
> and whoever of us can first review patches and:
>
> b4 am -s message-id
> git am foo.mbx
>
> Will get to apply patches. We can simply divide an conquer later and
> if needed send pull request etc, but the web gui crap, I'd really love
> to avoid it.
>
> But we need a list. Otherwise we gotta start Cc'ing everyone.
>
> Although we could abuse patches@lists.linux.dev it seems the timing
> is right for a mailing list dedicated for kdevops. Could we have one?
>
> [0] https://github.com/linux-kdevops/kdevops
>
+1 from me on requesting a mailing list. Discord is OK and all, but it's
not really a replacement for a mailing list for development. I think
this will help encourage more people to get involved as well.
I believe all we need to do is ask helpdesk@kernel.org:
https://subspace.kernel.org/lists.linux.dev.html#requesting-list-hosting
I like "kdevops@lists.linux.dev" .
I'm willing to be co-owner if you want a backup. I can't imagine it
involves a lot of administration anyway.
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2023-08-12 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 21:57 Mailing list request for kdevops enable persistent disks Luis Chamberlain
2023-08-12 12:21 ` Jeff Layton [this message]
2023-08-17 19:03 ` Luis Chamberlain
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=0b69bd4142afc5be0a8d76d00373d93317f609c3.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=a.manzanares@samsung.com \
--cc=amir73il@gmail.com \
--cc=chandan.babu@oracle.com \
--cc=josef@toxicpanda.com \
--cc=mcgrof@kernel.org \
--cc=patches@lists.linux.dev \
--cc=rt@kernel.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 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).