From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Bernd Krumboeck <krumboeck@universalnet.at>, linux-can@vger.kernel.org
Subject: Re: [PATCH] README: fix mainline linux typo + add linebreak
Date: Wed, 19 Jun 2013 08:54:55 +0200 [thread overview]
Message-ID: <51C155BF.10809@pengutronix.de> (raw)
In-Reply-To: <1371587622-21734-1-git-send-email-mkl@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]
On 06/18/2013 10:33 PM, Marc Kleine-Budde wrote:
> ---
> Hello Bernd,
>
> that was my first markdown patch, doesn't look as expected :( The documentation
> says two or more tailing spaces will be converted into <br />. And I wanted to
> say mainline linux.
>
> regards,
> Marc
>
> README.md | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/README.md b/README.md
> index 2b80717..8a32d0f 100644
> --- a/README.md
> +++ b/README.md
> @@ -3,7 +3,7 @@ CAN driver for UAB "8 devices" USB2CAN converter
>
> Note
> ----
> -The "8 devices" USB2CAN converter is supported by main linux since version 3.9.
> +The "8 devices" USB2CAN converter is supported by mainline linux since version 3.9.
The git magic (or you) removed the two trailing whitespace, according to
the original documentation two (or more) trailing whitespace are a line
break.
I wanted that this:
> THIS SOFTWARE COMES WITHOUT ANY WARRANTY!
to go into a separate line.
But I'm fine with the current README, no more patches :)
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
prev parent reply other threads:[~2013-06-19 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 20:33 [PATCH] README: fix mainline linux typo + add linebreak Marc Kleine-Budde
2013-06-19 4:01 ` Bernd Krumboeck
2013-06-19 6:54 ` Marc Kleine-Budde [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=51C155BF.10809@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=krumboeck@universalnet.at \
--cc=linux-can@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).