From: Sascha Hauer <s.hauer@pengutronix.de>
To: Lucas Stach <dev@lynxeye.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/2] docs: fix missing newlines in codeblocks
Date: Mon, 19 Jan 2015 08:46:20 +0100 [thread overview]
Message-ID: <20150119074620.GM18220@pengutronix.de> (raw)
In-Reply-To: <1421609904-14161-1-git-send-email-dev@lynxeye.de>
On Sun, Jan 18, 2015 at 08:38:23PM +0100, Lucas Stach wrote:
> Those cause a warning while generating the docs
> as well as misrendering of the generated docs.
>
> Signed-off-by: Lucas Stach <dev@lynxeye.de>
> ---
> Documentation/boards/garz-fricke.rst | 2 ++
> 1 file changed, 2 insertions(+)
Applied both, thanks
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2015-01-19 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 19:38 Lucas Stach
2015-01-18 19:38 ` [PATCH 2/2] docs: fix broken reference Lucas Stach
2015-01-19 7:46 ` Sascha Hauer [this message]
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=20150119074620.GM18220@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=dev@lynxeye.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