Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OpenEmbedded Development mailing list
	<openembedded-devel@lists.openembedded.org>
Subject: [PATCH] Aesthetic fix in chapter 1.
Date: Wed, 4 Nov 2009 03:09:17 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0911040306440.17282@localhost> (raw)


A simple tidy of a comma-separated list in Chapter 1.

Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>

---

  first in a list of patches to fix aesthetic stuff in user manual --
this patch is as trivial as it gets, but i would prefer to do this a
chapter at a time, if i might.  i promise that future patches will be
more substantive, but still be logically self-contained.

  is this the right format for submitting patches?  i'm just stealing
from the format for kernel patches.


diff --git a/docs/usermanual/chapters/introduction.xml b/docs/usermanual/chapters/introduction.xml
index 31f1f1f..28e7725 100644
--- a/docs/usermanual/chapters/introduction.xml
+++ b/docs/usermanual/chapters/introduction.xml
@@ -30,7 +30,7 @@
         </listitem>

         <listitem>
-          <para>Must be able to emit packages (tar, rpm, deb,ipk)</para>
+          <para>Must be able to emit packages (tar, rpm, deb, ipk)</para>
         </listitem>

         <listitem>


========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================



             reply	other threads:[~2009-11-04  8:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04  8:09 Robert P. J. Day [this message]
2009-11-04  8:25 ` [PATCH] Aesthetic fix in chapter 1 Holger Hans Peter Freyther

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=alpine.LFD.2.00.0911040306440.17282@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=openembedded-devel@lists.openembedded.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