From: Jonathan Corbet <corbet@lwn.net>
To: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
Cc: mchehab+samsung@kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [Linux-kernel-mentees] [PATCH v3 1/8] Documentation: nfsroot.txt: convert to ReST
Date: Fri, 10 Jan 2020 10:50:44 -0700 [thread overview]
Message-ID: <20200110105044.0877ad21@lwn.net> (raw)
In-Reply-To: <91ab26d120888f4f0a5fb535a42bf47ae5729238.1577917076.git.dwlsalmeida@gmail.com>
On Wed, 1 Jan 2020 19:26:08 -0300
"Daniel W. S. Almeida" <dwlsalmeida@gmail.com> wrote:
> From: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
>
> Convert nfsroot.txt to RST and move it to admin-guide. Content remains
> mostly the same.
>
> Signed-off-by: Daniel W. S. Almeida <dwlsalmeida@gmail.com>
*sigh*
So, I was ready to apply this whole set, finally, but couldn't do it. To
see why...
> Documentation/admin-guide/nfs/index.rst | 1 +
> .../nfs/nfsroot.rst} | 140 +++++++++---------
> 2 files changed, 75 insertions(+), 66 deletions(-)
> rename Documentation/{filesystems/nfs/nfsroot.txt => admin-guide/nfs/nfsroot.rst} (83%)
>
> diff --git a/Documentation/admin-guide/nfs/index.rst b/Documentation/admin-guide/nfs/index.rst
> index f5c0180f4e5e..c2b87e9f0fed 100644
> --- a/Documentation/admin-guide/nfs/index.rst
> +++ b/Documentation/admin-guide/nfs/index.rst
> @@ -6,4 +6,5 @@ NFS
> :maxdepth: 1
>
> nfs-client
> + nfsroot
Documentation/admin-guide/nfs doesn't exist in any tree I can see, and
neither does the nfs-client file referenced here. Which tree was this
generated against?
Can you make me a version that applies to docs-next, and we'll get it into
5.6?
Thanks,
jon
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2020-01-10 17:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 22:26 [Linux-kernel-mentees] [PATCH v3 0/8] Documentation: nfs: Convert a few documents to RST and move them to admin-guide Daniel W. S. Almeida
2020-01-01 22:26 ` [Linux-kernel-mentees] [PATCH v3 1/8] Documentation: nfsroot.txt: convert to ReST Daniel W. S. Almeida
2020-01-10 17:50 ` Jonathan Corbet [this message]
2020-01-01 22:26 ` [Linux-kernel-mentees] [PATCH v3 2/8] Documentation: nfsroot.rst: COSMETIC: refill a paragraph Daniel W. S. Almeida
2020-01-01 22:26 ` [Linux-kernel-mentees] [PATCH v3 3/8] Documentation: nfs-rdma: convert to ReST Daniel W. S. Almeida
2020-01-01 22:26 ` [Linux-kernel-mentees] [PATCH v3 4/8] Documentation: convert nfsd-admin-interfaces " Daniel W. S. Almeida
2020-01-01 22:26 ` [Linux-kernel-mentees] [PATCH v3 5/8] Documentation: nfs: idmapper: convert " Daniel W. S. Almeida
2020-01-01 22:26 ` [Linux-kernel-mentees] [PATCH v3 6/8] Documentation: nfs: convert pnfs-block-server " Daniel W. S. Almeida
2020-01-01 22:26 ` [Linux-kernel-mentees] [PATCH v3 7/8] Documentation: nfs: pnfs-scsi-server: convert " Daniel W. S. Almeida
2020-01-01 22:26 ` [Linux-kernel-mentees] [PATCH v3 8/8] Documentation: nfs: fault_injection: " Daniel W. S. Almeida
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=20200110105044.0877ad21@lwn.net \
--to=corbet@lwn.net \
--cc=dwlsalmeida@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@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).