All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Josef Bacik <josef@toxicpanda.com>
Cc: linux-fsdevel@vger.kernel.org, lsf-pc@lists.linux-foundation.org,
	kernel-team@fb.com
Subject: Re: [LSF/MM/BPF TOPIC] Changing how we do file system maintenance
Date: Tue, 16 Apr 2024 21:34:47 +0100	[thread overview]
Message-ID: <Zh7g5ws68IkJ1vo3@casper.infradead.org> (raw)
In-Reply-To: <20240416180414.GA2100066@perftesting>

On Tue, Apr 16, 2024 at 02:04:14PM -0400, Josef Bacik wrote:
> I would like to propose we organize ourselves more akin to the other
> large subsystems.  We are one of the few where everybody sends their
> own PR to Linus, so oftentimes the first time we're testing eachothers
> code is when we all rebase our respective trees onto -rc1.  I think
> we could benefit from getting more organized amongst ourselves, having
> a single tree we all flow into, and then have that tree flow into Linus.

This sounds like a great idea to me.  As someone who does a lot of
changes that touch a lot of filesystems, I'd benefit from this model.
It's very frustrating to be told "Oh, submit patches against tree X
which isn't included in linux-next".

A potential downside is that it increases the risk of an ntfs3 style
disaster where the code is essentially dumped on all other fs maintainers.
But I like the idea of a maintainer group which allows people to slide
in and out of the "patch pumpkin" role.  Particularly if it lets more
junior developers take a turn at wrangling patches.


  reply	other threads:[~2024-04-16 20:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16 18:04 [LSF/MM/BPF TOPIC] Changing how we do file system maintenance Josef Bacik
2024-04-16 20:34 ` Matthew Wilcox [this message]
2024-04-17 21:08   ` Kent Overstreet
2024-04-23  5:14     ` Steve French
2024-04-17  9:39 ` [Lsf-pc] " Jan Kara
2024-04-17 12:56 ` David Howells
2024-04-17 16:36 ` Christian Brauner
2024-04-18  0:54 ` Darrick J. Wong

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=Zh7g5ws68IkJ1vo3@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=josef@toxicpanda.com \
    --cc=kernel-team@fb.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.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.