From: Roland Hieber <r.hieber@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <r.hieber@pengutronix.de>
Subject: [ptxdist] [PATCH 3/4] doc: getting help: prune section with only one subsection
Date: Fri, 5 Oct 2018 11:45:17 +0200 [thread overview]
Message-ID: <20181005094518.29476-3-r.hieber@pengutronix.de> (raw)
In-Reply-To: <20181005094518.29476-1-r.hieber@pengutronix.de>
Previously several mailing lists were mentioned in this section, but now
it has been shrunk down to only the PTXdist mailing list. Reflect this
change in the section header.
Signed-off-by: Roland Hieber <r.hieber@pengutronix.de>
---
doc/getting_help.rst | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/doc/getting_help.rst b/doc/getting_help.rst
index 5a7613655..274e585ad 100644
--- a/doc/getting_help.rst
+++ b/doc/getting_help.rst
@@ -5,11 +5,8 @@ Below is a list of locations where you can get help in case of trouble.
For questions how to do something special with PTXdist or general
questions about Linux in the embedded world, try these.
-Mailing Lists
--------------
-
-About PTXdist in Particular
-~~~~~~~~~~~~~~~~~~~~~~~~~~~
+PTXdist Mailing List
+--------------------
This is an English language public mailing list for questions about
PTXdist. See
--
2.19.0
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-10-05 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 9:45 [ptxdist] [PATCH 1/4] doc: dev_manual: improve Patch Series section Roland Hieber
2018-10-05 9:45 ` [ptxdist] [PATCH 2/4] doc: contributing: fix typos, add links, and make text easier to parse Roland Hieber
2018-10-05 10:02 ` Roland Hieber
2018-10-05 9:45 ` Roland Hieber [this message]
2018-10-05 9:45 ` [ptxdist] [PATCH 4/4] doc: environment: general proof-reading and copy editing 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=20181005094518.29476-3-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