mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
Subject: [ptxdist] [PATCH v2 3/6] doc: pre-built packages: use consistent style in enumerations
Date: Wed, 13 Sep 2017 17:01:48 +0200	[thread overview]
Message-ID: <20170913150151.1592-4-u.oelmann@pengutronix.de> (raw)
In-Reply-To: <20170913150151.1592-1-u.oelmann@pengutronix.de>

Signed-off-by: Ulrich Ölmann <u.oelmann@pengutronix.de>
---
 doc/daily_work.inc | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/doc/daily_work.inc b/doc/daily_work.inc
index 5da0722c9bd6..e82e1724701f 100644
--- a/doc/daily_work.inc
+++ b/doc/daily_work.inc
@@ -676,7 +676,7 @@ Please be careful when using the pre-built archives if you:
    package is under development.
 
 -  change the hard coded configure settings in the package’s rule file,
-   e.g. a package is under development
+   e.g. a package is under development.
 
 -  intend to use one pre-built archive pool from different PTXdist
    projects.
@@ -696,16 +696,16 @@ archives. These kind of packages are always (re-)built.
 Only target related packages can be used based on their pre-built
 archives, but there are a few exceptions:
 
--  Linux kernel: It has an incomplete install stage, which results into
+-  Linux kernel: it has an incomplete install stage, which results into
    an incomplete pre-built archive. Due to this, it cannot be used as a
-   pre-built archive
+   pre-built archive.
 
--  Barebox bootloader: It has an incomplete install stage, which results
+-  Barebox bootloader: it has an incomplete install stage, which results
    into an incomplete pre-built archive. Due to this, it cannot be used
-   as a pre-built archive
+   as a pre-built archive.
 
 -  some other somehow broken packages all marked with a
-   ``<packagename>_DEVPKG := NO`` in their corresponding rule file
+   ``<packagename>_DEVPKG := NO`` in their corresponding rule file.
 
 Workflow with Pre-Built Archives
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -749,10 +749,10 @@ Use Cases
 
 Some major possible use cases are covered in this section:
 
--  Speed up a re-build of one single project
+-  speed up a re-build of one single project.
 
--  Sharing pre-built archives between two platforms based on the same
-   architecture
+-  sharing pre-built archives between two platforms based on the same
+   architecture.
 
 To simply speed up a re-build of the whole project (without development
 on any of the used packages) we just can copy all ``*-dev.tar.gz``
-- 
2.11.0


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  parent reply	other threads:[~2017-09-13 15:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-13 15:01 [ptxdist] [PATCH v2 0/6] doc: pre-built packages: review chapter 'Using Pre-Built Archives' Ulrich Ölmann
2017-09-13 15:01 ` [ptxdist] [PATCH v2 1/6] doc: pre-built packages: fix typos Ulrich Ölmann
2017-09-13 15:01 ` [ptxdist] [PATCH v2 2/6] doc: pre-built packages: adjust capitalization in headings Ulrich Ölmann
2017-09-13 15:01 ` Ulrich Ölmann [this message]
2017-09-13 15:01 ` [ptxdist] [PATCH v2 4/6] doc: pre-built packages: english genitive uses an apostrophe Ulrich Ölmann
2017-09-13 15:01 ` [ptxdist] [PATCH v2 5/6] doc: pre-built packages: enhance phrasing Ulrich Ölmann
2017-09-13 15:01 ` [ptxdist] [PATCH v2 6/6] doc: pre-built packages: some additions Ulrich Ölmann

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=20170913150151.1592-4-u.oelmann@pengutronix.de \
    --to=u.oelmann@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