From: "Tobin C. Harding" <me@tobin.cc>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
linux-doc@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] docs: bpf: Rename README.rst to index.rst
Date: Thu, 26 Jul 2018 08:28:23 +1000 [thread overview]
Message-ID: <20180725222823.GD6067@eros> (raw)
In-Reply-To: <0141716c-e909-1429-68fe-6da71d4c6677@cogentembedded.com>
On Wed, Jul 25, 2018 at 12:29:10PM +0300, Sergei Shtylyov wrote:
> Hello!
>
> On 7/25/2018 5:29 AM, Tobin C. Harding wrote:
>
> > Recently bpf/ docs were converted to us RST format. 'README.rst' was
>
> s/us/use/?
Thanks for the review Sergei, will fix and re-spin.
> > created but in order to fit in with the Sphinx build system this file
> > should be named 'index.rst'. Rename file, fixes to integrate into Sphinx
> > build system in following patches.
> >
> > docs: Rename Documentation/bpf/README.rst to Documentation/bpf/index.rst
> >
> > Signed-off-by: Tobin C. Harding <me@tobin.cc>
> [...]
>
> MBR, Sergei
What does MBR stand for please (not master boot record I'm guessing)?
Tobin
next prev parent reply other threads:[~2018-07-25 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 2:29 [PATCH 0/4] docs: bpf: Fix RST conversion Tobin C. Harding
2018-07-25 2:29 ` [PATCH 1/4] docs: bpf: Rename README.rst to index.rst Tobin C. Harding
2018-07-25 9:29 ` Sergei Shtylyov
2018-07-25 22:28 ` Tobin C. Harding [this message]
2018-07-26 7:48 ` Sergei Shtylyov
2018-07-25 2:29 ` [PATCH 2/4] docs: bpf: Add toctree to index Tobin C. Harding
2018-07-25 2:29 ` [PATCH 3/4] docs: Add bpf/index to top level index Tobin C. Harding
2018-07-25 2:29 ` [PATCH 4/4] docs: bpf: Capitalise document heading Tobin C. Harding
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=20180725222823.GD6067@eros \
--to=me@tobin.cc \
--cc=ast@kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
/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).