Linux EXT4 FS development
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Matthias Goergens <matthias.goergens@gmail.com>
Cc: Theodore Ts'o <tytso@mit.edu>, Jan Kara <jack@suse.cz>,
	linux-ext4@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: name the ext4 dev branch
Date: Wed, 23 Sep 2026 21:00:30 -0700	[thread overview]
Message-ID: <20260924040030.GB5048@sol> (raw)
In-Reply-To: <20260924033200.3615554-1-matthias.goergens@gmail.com>

On Thu, Sep 24, 2026 at 11:32:00AM +0800, Matthias Goergens wrote:
> For the entries, my plan is to start with the roughly 160 T: lines
> that name a repository whose HEAD is already in mainline while
> linux-next pulls a different branch from it: one small patch per
> repository, sent to that entry's maintainers as its own thread.  I'd
> send a few first, to maintainers who usually respond quickly, and then
> the rest in larger batches once the first ones have landed or drawn
> comments.  You know far better than I do how maintainers take this
> kind of tree-wide cleanup, so I'd welcome your view on that approach
> before I start.

Explicitly documenting branches in MAINTAINERS sounds good, but in
addition to that, HEAD should also be made to point to the correct
branch (at least in repositories where there is only one main
development branch).  This can be done using gitolite's symbolic-ref
command: https://korg.docs.kernel.org/gitolite/index.html#symbolic-ref

That is how https://git.kernel.org/pub/scm/fs/fscrypt/linux.git points
to the 'for-next' branch by default, for example.

- Eric

  reply	other threads:[~2026-09-24  4:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23 10:17 [PATCH] MAINTAINERS: name the ext4 dev branch Matthias Goergens
2026-09-23 10:44 ` Jan Kara
2026-09-24  3:14 ` Theodore Tso
2026-09-24  3:32   ` Matthias Goergens
2026-09-24  4:00     ` Eric Biggers [this message]
2026-09-24  8:30       ` Matthias Goergens
2026-09-24  8:53       ` Jan Kara
2026-09-25 13:06       ` Niklas Cassel
2026-09-25 18:43         ` Eric Biggers
2026-09-26  6:11         ` Matthias Goergens
2026-09-26 15:57           ` Niklas Cassel
2026-10-01 11:25     ` Matthias Goergens
2026-10-08 15:32 ` Theodore Ts'o

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=20260924040030.GB5048@sol \
    --to=ebiggers@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=matthias.goergens@gmail.com \
    --cc=tytso@mit.edu \
    /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