From: Steve Kowalik <steven@wedontsleep.org>
To: linux-sh@vger.kernel.org
Subject: [PATCH 0/2] convert sh interfaces to RST
Date: Fri, 24 Feb 2017 07:38:36 +0000 [thread overview]
Message-ID: <1487921918-25203-1-git-send-email-steven@wedontsleep.org> (raw)
Convert the SuperH interfaces guide to RST, and add a new arch-guide to
place it into. I'm not hugely happy with the wording, but I've been sitting
on this long enough, and should get more eyes on it.
Steve Kowalik (2):
Documentation: convert sh interfaces to RST
Documentation: Add arch-guide documentation
Documentation/00-INDEX | 2 +
Documentation/DocBook/Makefile | 2 +-
Documentation/DocBook/sh.tmpl | 105 -------------------------------------
Documentation/arch-guide/conf.py | 10 ++++
Documentation/arch-guide/index.rst | 14 +++++
Documentation/index.rst | 11 ++++
Documentation/sh/interfaces.rst | 63 ++++++++++++++++++++++
7 files changed, 101 insertions(+), 106 deletions(-)
delete mode 100644 Documentation/DocBook/sh.tmpl
create mode 100644 Documentation/arch-guide/conf.py
create mode 100644 Documentation/arch-guide/index.rst
create mode 100644 Documentation/sh/interfaces.rst
--
2.7.4
reply other threads:[~2017-02-24 7:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1487921918-25203-1-git-send-email-steven@wedontsleep.org \
--to=steven@wedontsleep.org \
--cc=linux-sh@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).