mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Christoph G . Baumann" <chris@sgoc.de>,
	Roland Hieber <rhi@pengutronix.de>
Subject: [ptxdist] [PATCH] doc: daily work: multi images: fix typos and apply more markup
Date: Tue, 26 Feb 2019 16:32:23 +0100	[thread overview]
Message-ID: <20190226153223.7159-1-rhi@pengutronix.de> (raw)

Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
 doc/multi_image_platforms.inc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/multi_image_platforms.inc b/doc/multi_image_platforms.inc
index a90393839..2a8444391 100644
--- a/doc/multi_image_platforms.inc
+++ b/doc/multi_image_platforms.inc
@@ -60,20 +60,20 @@ There are two ways to mange the package list for the image:
 
      IMAGE_ROOT_BOARD_A_PKGS := $(PTX_PACKAGES_INSTALL) board-a-extra
 
-   This is not recommended for larger changes to the packages list. Is is easy
+   This is not recommended for larger changes to the packages list, as it is easy
    to break dependencies this way.
 
 2. Use a collection config to create the package list
 
    To prepare for this, all packages that are not part of _all_ variants
-   must be set 'M' in menuconfig.
+   must be set ``M`` in menuconfig.
 
    Then a new collection for the variant is created:
 
    .. code-block:: text
 
      $ touch configs/collectionconfig-board-a
-     $ ptxdist ----collectionconfig=configs/collectionconfig-board-a menuconfig collection
+     $ ptxdist --collectionconfig=configs/collectionconfig-board-a menuconfig collection
 
    All extra packages for this variant are selected here. Then the
    collection config is configured for the image:
-- 
2.20.1


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

                 reply	other threads:[~2019-02-26 15:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20190226153223.7159-1-rhi@pengutronix.de \
    --to=rhi@pengutronix.de \
    --cc=chris@sgoc.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