patches.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: rt@kernel.org, chandan.babu@oracle.com, jlayton@kernel.org,
	amir73il@gmail.com, josef@toxicpanda.com,
	a.manzanares@samsung.com
Cc: patches@lists.linux.dev
Subject: Mailing list request for kdevops enable persistent disks
Date: Thu, 3 Aug 2023 14:57:58 -0700	[thread overview]
Message-ID: <ZMwi5oDiAKGpPh8B@bombadil.infradead.org> (raw)

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

  Luis

             reply	other threads:[~2023-08-03 21:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03 21:57 Luis Chamberlain [this message]
2023-08-12 12:21 ` Mailing list request for kdevops enable persistent disks Jeff Layton
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=ZMwi5oDiAKGpPh8B@bombadil.infradead.org \
    --to=mcgrof@kernel.org \
    --cc=a.manzanares@samsung.com \
    --cc=amir73il@gmail.com \
    --cc=chandan.babu@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=josef@toxicpanda.com \
    --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).