From: "Michael Opdenacker" <michael.opdenacker@bootlin.com>
To: docs@lists.yoctoproject.org
Subject: Fix suspicious newlines
Date: Tue, 30 Mar 2021 14:15:39 +0200 [thread overview]
Message-ID: <20210330121540.10101-1-michael.opdenacker@bootlin.com> (raw)
Greetings,
This is a first batch of updates for you to review before
I continue.
There seems to be many more newline issues like these,
which could reveal potential documentation migration issues.
I'll carefully review each type.
Thanks in advance
Michael.
next reply other threads:[~2021-03-30 12:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 12:15 Michael Opdenacker [this message]
2021-03-30 12:15 ` [PATCH] Fix suspicious newlines Michael Opdenacker
[not found] ` <16711DDA4F8BFBC9.20186@lists.yoctoproject.org>
2021-03-30 12:21 ` [docs] " Michael Opdenacker
[not found] ` <16711E294AEE4A72.27664@lists.yoctoproject.org>
2021-04-06 20:20 ` Michael Opdenacker
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=20210330121540.10101-1-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.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