linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: update btrfs website links and files
Date: Tue, 11 Oct 2022 15:48:55 -0700	[thread overview]
Message-ID: <CAHk-=wiB9sHzsNcCRRkgeyXLu09hV-FgRLwvFHoA_uCpZRJJwA@mail.gmail.com> (raw)
In-Reply-To: <20221011132256.333-1-dsterba@suse.com>

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

  reply	other threads:[~2022-10-11 22:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 13:22 [PATCH] MAINTAINERS: update btrfs website links and files David Sterba
2022-10-11 22:48 ` Linus Torvalds [this message]
2022-10-12 10:29   ` David Sterba

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='CAHk-=wiB9sHzsNcCRRkgeyXLu09hV-FgRLwvFHoA_uCpZRJJwA@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).