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 4/6] doc: pre-built packages: english genitive uses an apostrophe
Date: Wed, 13 Sep 2017 17:01:49 +0200	[thread overview]
Message-ID: <20170913150151.1592-5-u.oelmann@pengutronix.de> (raw)
In-Reply-To: <20170913150151.1592-1-u.oelmann@pengutronix.de>

Exchange U+2019 (right single quotation mark) by a simple apostrophe.

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 e82e1724701f..34be5aa4c535 100644
--- a/doc/daily_work.inc
+++ b/doc/daily_work.inc
@@ -569,7 +569,7 @@ development machine.
 Using Pre-Built Archives
 ------------------------
 
-PTXdist is a tool which creates all the required parts of a target’s
+PTXdist is a tool which creates all the required parts of a target's
 filesystem to breathe life into it. And it creates these parts from any
 kind of source files. If a PTXdist project consists of many packages the
 build may take a huge amount of time.
@@ -589,9 +589,9 @@ re-building everything from time to time is a very good test case if
 some adaptions are still missing or if everything is complete, it can be
 a real time sink to do so.
 
-To not lose developer’s temper when doing such tests, PTXdist can keep
-archives from the last run which includes all the files the package’s
-build system has installed while the PTXdist’s *install* stage runs for
+To not lose developer's temper when doing such tests, PTXdist can keep
+archives from the last run which includes all the files the package's
+build system has installed while the PTXdist's *install* stage runs for
 it.
 
 The next time PTXdist should build a package it can use the results from
@@ -642,10 +642,10 @@ build in the menu:
 
 With the next build (e.g. ``ptxdist go``) PTXdist will look for a
 specific package if its corresponding pre-built archive does exist. If
-it does exist and the used hash value in the pre-built archive’s
+it does exist and the used hash value in the pre-built archive's
 filename matches, PTXdist will skip all source archive handling
 (extract, patch, compile and install) and just extract and use the
-pre-built archive’s content.
+pre-built archive's content.
 
 A regular and safe usecase of pre-built archives is:
 
@@ -658,8 +658,8 @@ A regular and safe usecase of pre-built archives is:
 -  no package with a pre-built archive in the project is under
    development.
 
-The hash as a part of the pre-built archive’s filename does only reflect
-the package’s configuration made in the menu (``ptxdist menuconfig``).
+The hash as a part of the pre-built archive's filename does only reflect
+the package's configuration made in the menu (``ptxdist menuconfig``).
 If this package specific configuration changes, a new hash value will be
 the result and PTXdist can select the corresponding correct pre-built
 archive.
@@ -675,7 +675,7 @@ Please be careful when using the pre-built archives if you:
 -  change the patch set applied to the corresponding package, e.g. a
    package is under development.
 
--  change the hard coded configure settings in the package’s rule file,
+-  change the hard coded configure settings in the package's rule file,
    e.g. a package is under development.
 
 -  intend to use one pre-built archive pool from different PTXdist
-- 
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 ` [ptxdist] [PATCH v2 3/6] doc: pre-built packages: use consistent style in enumerations Ulrich Ölmann
2017-09-13 15:01 ` Ulrich Ölmann [this message]
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-5-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