From: Matthew Wilcox <willy@infradead.org>
To: Dave Chinner <dchinner@redhat.com>
Cc: Charles Han <hanchunchao@inspur.com>,
corbet@lwn.net, djwong@kernel.org, allison.henderson@oracle.com,
bhelgaas@google.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] Documentation: xfs: Remove repeated word in comments
Date: Tue, 19 Sep 2023 22:15:21 +0100 [thread overview]
Message-ID: <ZQoPaXNAwtu4wl02@casper.infradead.org> (raw)
In-Reply-To: <ZQoMqI/QGPWEpkEi@rh>
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
On Wed, Sep 20, 2023 at 07:03:36AM +1000, Dave Chinner wrote:
> [cc linux-xfs@vger.kernel.org]
>
> Hi Charles,
>
> For future reference, can you CC the XFS list on XFS documentation
> changes please? That's much preferable to sending patches to random
> developers and hoping they notice it....
>
> On Mon, Sep 18, 2023 at 03:19:05PM +0800, Charles Han wrote:
> > Remove the repeated word "the" in comments.
> >
> > Signed-off-by: Charles Han <hanchunchao@inspur.com>
> > ---
> > Documentation/filesystems/xfs-online-fsck-design.rst | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/filesystems/xfs-online-fsck-design.rst b/Documentation/filesystems/xfs-online-fsck-design.rst
To be fair, this new file isn't listed in MAINTAINERS, so
scripts/get_maintainer.pl doesn't know about it. May I
suggest the attached patch?
[-- Attachment #2: 0001-XFS-Update-MAINTAINERS-to-catch-all-XFS-documentatio.patch --]
[-- Type: text/plain, Size: 1064 bytes --]
From e0eb2f0d1425e6a5dae23c983eb793afa5d040c1 Mon Sep 17 00:00:00 2001
From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Date: Tue, 19 Sep 2023 17:12:45 -0400
Subject: [PATCH] XFS: Update MAINTAINERS to catch all XFS documentation
Assumes that all XFS documentation will be prefixed with xfs-, which
seems like a good policy anyway.
Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
---
MAINTAINERS | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index bf0f54c24f81..3554195022ee 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -23640,8 +23640,7 @@ T: git git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
P: Documentation/filesystems/xfs-maintainer-entry-profile.rst
F: Documentation/ABI/testing/sysfs-fs-xfs
F: Documentation/admin-guide/xfs.rst
-F: Documentation/filesystems/xfs-delayed-logging-design.rst
-F: Documentation/filesystems/xfs-self-describing-metadata.rst
+F: Documentation/filesystems/xfs-*
F: fs/xfs/
F: include/uapi/linux/dqblk_xfs.h
F: include/uapi/linux/fsmap.h
--
2.40.1
next prev parent reply other threads:[~2023-09-19 21:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230918071905.296081-1-hanchunchao@inspur.com>
2023-09-19 21:03 ` [PATCH] Documentation: xfs: Remove repeated word in comments Dave Chinner
2023-09-19 21:15 ` Matthew Wilcox [this message]
2023-09-19 21:55 ` Dave Chinner
2023-09-19 22:09 ` Darrick J. Wong
2023-09-27 12:27 ` Chandan Babu R
2023-09-19 22:10 ` Darrick J. Wong
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=ZQoPaXNAwtu4wl02@casper.infradead.org \
--to=willy@infradead.org \
--cc=allison.henderson@oracle.com \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=hanchunchao@inspur.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@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).