linux-kernel - Re: [PATCH] MAINTAINERS: update btrfs website links and files

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20221012102917.GV13389@suse.cz>
Date:   Wed, 12 Oct 2022 12:29:17 +0200
From:   David Sterba <dsterba@...e.cz>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     David Sterba <dsterba@...e.com>, linux-btrfs@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: update btrfs website links and files

On Tue, Oct 11, 2022 at 03:48:55PM -0700, Linus Torvalds wrote:
> On Tue, Oct 11, 2022 at 6:23 AM David Sterba <dsterba@...e.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.

Yeah the reason was because it's out of my directory, the exports to mm/
or fs/ were necessary for code to work but the maintainers file is
plain text, I thought there was a different workflow.

> 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.

Sorry for confusion, you can ignore the patch. I'll add it to the pulled
branch, like last time which was not that long ago (mid 2021, commit
503d1acb01826b42e) but I forgot about that.