From: "Tobin C. Harding" <me@tobin.cc>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Tobin C. Harding" <me@tobin.cc>,
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: [PATCH 1/4] docs: bpf: Rename README.rst to index.rst
Date: Wed, 25 Jul 2018 12:29:23 +1000 [thread overview]
Message-ID: <20180725022926.8993-2-me@tobin.cc> (raw)
In-Reply-To: <20180725022926.8993-1-me@tobin.cc>
Recently bpf/ docs were converted to us RST format. 'README.rst' was
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>
---
Documentation/bpf/{README.rst => index.rst} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename Documentation/bpf/{README.rst => index.rst} (100%)
diff --git a/Documentation/bpf/README.rst b/Documentation/bpf/index.rst
similarity index 100%
rename from Documentation/bpf/README.rst
rename to Documentation/bpf/index.rst
--
2.17.1
next prev parent reply other threads:[~2018-07-25 2:29 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 ` Tobin C. Harding [this message]
2018-07-25 9:29 ` [PATCH 1/4] docs: bpf: Rename README.rst to index.rst Sergei Shtylyov
2018-07-25 22:28 ` Tobin C. Harding
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=20180725022926.8993-2-me@tobin.cc \
--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 \
/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).