Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20221011132256.333-1-dsterba@suse.com>
In-Reply-To: <20221011132256.333-1-dsterba@suse.com>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue, 11 Oct 2022 15:48:55 -0700
Message-ID: <CAHk-=wiB9sHzsNcCRRkgeyXLu09hV-FgRLwvFHoA_uCpZRJJwA@mail.gmail.com>
Subject: Re: [PATCH] MAINTAINERS: update btrfs website links and files
To:     David Sterba <dsterba@suse.com>
Cc:     linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Tue, Oct 11, 2022 at 6:23 AM David Sterba <dsterba@suse.com> wrote:
>
> We have the new documentation hosted on Read The Docs and content is
> migrated there from the wiki. Also update http to https and add the
> tracepoint definition header.

Hmm. Did you intend for me to apply this as a patch?

Since you normally just send pull requests, I'm a bit confused.

Is this a "it's outside the btrfs subdirectory, so I'm sending this as
a patch"? Except I've seen you send stuff that has changes to mm/ for
new exports etc, and in fact to MAINTAINERS too.

Or is this just an informational "let Linus know about this patch" email?

Anyway, if you actually want me to apply a patch directly because of
some "I'm not going to send this as a pull request because there is
nothing else pending" kind of issue or other reason, please do state
that explicitly in the email.

Because as it is now, as explained above, I'm not sure why this patch
was sent to me.

               Linus