From: Sheriff Esseson <sheriffesseson@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
darrick.wong@oracle.com, linux-xfs@vger.kernel.org,
corbet@lwn.net, linux-doc@vger.kernel.org
Subject: Re: [Linux-kernel-mentees] [PATCH] Doc : fs : move xfs.txt to admin-guide
Date: Fri, 5 Jul 2019 20:41:48 +0100 [thread overview]
Message-ID: <20190705193329.GA20933@localhost> (raw)
In-Reply-To: <20190705190412.GB32320@bombadil.infradead.org>
On Fri, Jul 05, 2019 at 12:04:12PM -0700, Matthew Wilcox wrote:
> On Fri, Jul 05, 2019 at 02:14:46PM +0100, Sheriff Esseson wrote:
> > As suggested by Matthew Wilcox, xfs.txt is primarily a guide on available
> > options when setting up an XFS. This makes it appropriate to be placed under
> > the admin-guide tree.
> >
> > Thus, move xfs.txt to admin-guide and fix broken references.
>
> What happened to the conversion to xfs.rst?
Okay, I was thinking placing the file properly should come first before the
conversion.
I'll continue work on the conversion right away. I'll send it on Monday, letting
the dust settle on this one.
>
> _______________________________________________
> Linux-kernel-mentees mailing list
> Linux-kernel-mentees@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
thanks.
next prev parent reply other threads:[~2019-07-05 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 13:14 [Linux-kernel-mentees] [PATCH] Doc : fs : move xfs.txt to admin-guide Sheriff Esseson
2019-07-05 19:04 ` Matthew Wilcox
2019-07-05 19:41 ` Sheriff Esseson [this message]
2019-07-08 19:59 ` Matthew Wilcox
2019-07-08 20:00 ` Christoph Hellwig
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=20190705193329.GA20933@localhost \
--to=sheriffesseson@gmail.com \
--cc=corbet@lwn.net \
--cc=darrick.wong@oracle.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-xfs@vger.kernel.org \
--cc=willy@infradead.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).