From: Roland Hieber <r.hieber@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH v2 2/5] doc: promote faq to own section
Date: Fri, 14 Jul 2017 15:47:48 +0200 [thread overview]
Message-ID: <20170714134751.21182-2-r.hieber@pengutronix.de> (raw)
In-Reply-To: <20170714134751.21182-1-r.hieber@pengutronix.de>
Signed-off-by: Roland Hieber <r.hieber@pengutronix.de>
---
doc/daily_work_section.rst | 1 -
doc/{faq.inc => faq.rst} | 0
doc/index.rst | 1 +
3 files changed, 1 insertion(+), 1 deletion(-)
rename doc/{faq.inc => faq.rst} (100%)
diff --git a/doc/daily_work_section.rst b/doc/daily_work_section.rst
index daec36dca..0e4e6e767 100644
--- a/doc/daily_work_section.rst
+++ b/doc/daily_work_section.rst
@@ -5,4 +5,3 @@ Various Aspects of Daily Work
.. include:: nfsroot.inc
.. include:: working_with_git_sources.inc
.. include:: including_bsp_doc.inc
-.. include:: faq.inc
diff --git a/doc/faq.inc b/doc/faq.rst
similarity index 100%
rename from doc/faq.inc
rename to doc/faq.rst
diff --git a/doc/index.rst b/doc/index.rst
index 9aad6cddb..7ab42d4c7 100644
--- a/doc/index.rst
+++ b/doc/index.rst
@@ -17,6 +17,7 @@ Welcome to the PTXdist Universe
dev_manual
ref_manual
daily_work_section
+ faq
getting_help
* :ref:`search`
--
2.11.0
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-07-14 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 13:47 [ptxdist] [PATCH v2 1/5] doc: document git patch workflow Roland Hieber
2017-07-14 13:47 ` Roland Hieber [this message]
2017-07-14 13:47 ` [ptxdist] [PATCH v2 3/5] doc: faq: apply more structure Roland Hieber
2017-07-14 13:47 ` [ptxdist] [PATCH v2 4/5] doc: faq: copy editing, small rewrites for more clarity Roland Hieber
2017-07-14 13:47 ` [ptxdist] [PATCH 5/5] doc: css: use more ptxdist-like colors for admonitions Roland Hieber
2017-07-17 23:20 ` [ptxdist] [PATCH v3 1/5] doc: document git patch workflow Roland Hieber
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=20170714134751.21182-2-r.hieber@pengutronix.de \
--to=r.hieber@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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