[PATCH] MAINTAINERS: update btrfs git tree entries

[PATCH] MAINTAINERS: update btrfs git tree entries

[David Sterba]

Add new entry pointing to the development branch so e.g. sashiko can
pick it as the baseline. The other entry is for linux-next and slightly
behind.

Signed-off-by: David Sterba <dsterba@suse.com>
---
 MAINTAINERS | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 58a0875d4f01..c9ee9dbb657d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5623,7 +5623,8 @@ S:	Maintained
 W:	https://btrfs.readthedocs.io
 Q:	https://patchwork.kernel.org/project/linux-btrfs/list/
 C:	irc://irc.libera.chat/btrfs
-T:	git git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git
+T:	git https://github.com/btrfs/linux.git for-next
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
 F:	Documentation/filesystems/btrfs.rst
 F:	fs/btrfs/
 F:	include/linux/btrfs*
-- 
2.55.0

Re: [PATCH] MAINTAINERS: update btrfs git tree entries

[Linus Torvalds]

On Wed, 19 Aug 2026 at 03:28, David Sterba <dsterba@suse.com> wrote:
>
> Add new entry pointing to the development branch so e.g. sashiko can
> pick it as the baseline. The other entry is for linux-next and slightly
> behind.

So I expected this to come in with the btrfs pull, but it didn't. So I
applied it directly, which I assume you wanted.

Just as a general workflow issue: I typically think that patches I see
are sent out as a FYI kind of thing - particularly when they come from
people who normally send me a git pull request.

So if you actually want expect me to apply said patch directly, please
do say so explicitly, so that it doesn't end up being one of these
"what was the expectation for this patch" issues...

As it is, I kind of have to guess from the context ("was I cc'd or the
main recipient, did I get a pull request or not").

                  Linus

Re: [PATCH] MAINTAINERS: update btrfs git tree entries

[David Sterba]

On Sun, Aug 23, 2026 at 09:34:24AM -0700, Linus Torvalds wrote:
> On Wed, 19 Aug 2026 at 03:28, David Sterba <dsterba@suse.com> wrote:
> >
> > Add new entry pointing to the development branch so e.g. sashiko can
> > pick it as the baseline. The other entry is for linux-next and slightly
> > behind.
> 
> So I expected this to come in with the btrfs pull, but it didn't. So I
> applied it directly, which I assume you wanted.

Yes indeed, thanks.

> Just as a general workflow issue: I typically think that patches I see
> are sent out as a FYI kind of thing - particularly when they come from
> people who normally send me a git pull request.
> 
> So if you actually want expect me to apply said patch directly, please
> do say so explicitly, so that it doesn't end up being one of these
> "what was the expectation for this patch" issues...
> 
> As it is, I kind of have to guess from the context ("was I cc'd or the
> main recipient, did I get a pull request or not").

I should have mentioned it under the "--" marker, sorry. The reason was
the pull request was not ready at that time and guys were noticing too
many patches dropped by sashiko due to incorrect base.  Sending the git
URL/branch change to speed things up sounded like a good idea to me.