From: David Sterba <dsterba@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Sterba <dsterba@suse.com>,
linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: update btrfs git tree entries
Date: Mon, 24 Aug 2026 17:47:30 +0200 [thread overview]
Message-ID: <20260824154730.GE9053@twin.jikos.cz> (raw)
In-Reply-To: <CAHk-=whWQKHpgAWUm=REzpD=t2DWn2_WVNMDXAerh3J9N3fG1g@mail.gmail.com>
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.
prev parent reply other threads:[~2026-08-24 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 10:28 [PATCH] MAINTAINERS: update btrfs git tree entries David Sterba
2026-08-23 16:34 ` Linus Torvalds
2026-08-24 15:47 ` David Sterba [this message]
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=20260824154730.GE9053@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox