Skip to contentSkip to conversation

MAINTAINERS: update btrfs git tree entries

PATCH In review David Sterba 3 participants 3 messages Aug 19 – Aug 24 Btrfs file system

lore
Share & tools
lore

David Sterba

author maintainer
#0 lore raw

PATCH 1/1 MAINTAINERS: update btrfs git tree entries

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.

---
 MAINTAINERS | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
MAINTAINERS +2 -1
index 58a0875d4f01..c9ee9dbb657d 100644
@@ -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*
Signature · 1 line
2.55.0
#1 lore raw
Quoted 4 lines · 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.

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

#2 lore raw
Quoted 8 lines · Linus Torvalds
Quoted 4 lines · 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.

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.

Quoted 10 lines

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.