patches.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
* Mailing list request for kdevops enable persistent disks
@ 2023-08-03 21:57 Luis Chamberlain
  2023-08-12 12:21 ` Jeff Layton
  0 siblings, 1 reply; 3+ messages in thread
From: Luis Chamberlain @ 2023-08-03 21:57 UTC (permalink / raw)
  To: rt, chandan.babu, jlayton, amir73il, josef, a.manzanares; +Cc: patches

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Mailing list request for kdevops enable persistent disks
  2023-08-03 21:57 Mailing list request for kdevops enable persistent disks Luis Chamberlain
@ 2023-08-12 12:21 ` Jeff Layton
  2023-08-17 19:03   ` Luis Chamberlain
  0 siblings, 1 reply; 3+ messages in thread
From: Jeff Layton @ 2023-08-12 12:21 UTC (permalink / raw)
  To: Luis Chamberlain, rt, chandan.babu, amir73il, josef, a.manzanares; +Cc: patches

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>

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Mailing list request for kdevops enable persistent disks
  2023-08-12 12:21 ` Jeff Layton
@ 2023-08-17 19:03   ` Luis Chamberlain
  0 siblings, 0 replies; 3+ messages in thread
From: Luis Chamberlain @ 2023-08-17 19:03 UTC (permalink / raw)
  To: Jeff Layton; +Cc: rt, chandan.babu, amir73il, josef, a.manzanares, patches

We have a mailing list now:

https://lore.kernel.org/kdevops/
https://subspace.kernel.org/lists.linux.dev.html

  Luis

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2023-08-17 19:04 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-08-03 21:57 Mailing list request for kdevops enable persistent disks Luis Chamberlain
2023-08-12 12:21 ` Jeff Layton
2023-08-17 19:03   ` Luis Chamberlain

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).