From: Alexander Smirnov <asmirnov@ilbers.de>
To: isar-users@googlegroups.com
Cc: Alexander Smirnov <asmirnov@ilbers.de>
Subject: [PATCH 5/5] doc/technical_overview: Fix formatting
Date: Sun, 27 Aug 2017 17:38:40 +0300 [thread overview]
Message-ID: <20170827143840.12436-6-asmirnov@ilbers.de> (raw)
In-Reply-To: <20170827143840.12436-1-asmirnov@ilbers.de>
Break a long line at column 78.
Signed-off-by: Alexander Smirnov <asmirnov@ilbers.de>
---
doc/technical_overview.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/doc/technical_overview.md b/doc/technical_overview.md
index a4563b3..20e08b4 100644
--- a/doc/technical_overview.md
+++ b/doc/technical_overview.md
@@ -121,7 +121,9 @@ All these steps are described in details below.
## 3.2 Initial Buildchroot Generation
-As mentioned above, initial buildchroot is generated using multistrap. The bitbake recipe which is responsible for buildchroot can be found here: `meta/recipes-devtools/buildchroot/buildchroot.bb`
+As mentioned above, initial buildchroot is generated using multistrap. The
+bitbake recipe which is responsible for buildchroot can be found here:
+`meta/recipes-devtools/buildchroot/buildchroot.bb`
This recipe implementes `do_build` task which performs the following:
--
2.1.4
prev parent reply other threads:[~2017-08-27 14:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-27 14:38 [PATCH 0/5] Isar fixes Alexander Smirnov
2017-08-27 14:38 ` [PATCH 1/5] classes/base: Fix fetch task dependency Alexander Smirnov
2017-08-28 14:57 ` Henning Schild
2017-08-29 6:27 ` Alexander Smirnov
2017-08-29 7:43 ` Henning Schild
2017-08-29 7:54 ` Alexander Smirnov
2017-08-27 14:38 ` [PATCH 2/5] meta-isar/hello: Update recipe version Alexander Smirnov
2017-08-27 14:38 ` [PATCH 3/5] debian/stretch: Use ftp.d.o instead of deb.d.o Alexander Smirnov
2017-08-27 14:38 ` [PATCH 4/5] scripts/ci_build: Update build script Alexander Smirnov
2017-08-27 14:38 ` Alexander Smirnov [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=20170827143840.12436-6-asmirnov@ilbers.de \
--to=asmirnov@ilbers.de \
--cc=isar-users@googlegroups.com \
/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