All of lore.kernel.org
 help / color / mirror / Atom feed
From: tom.zanussi@intel.com
To: scott.m.rifenbark@intel.com, rpjday@crashcourse.ca,
	yocto@yoctoproject.org
Subject: [PATCH 0/3] yocto-docs/bsp-guide: update BSP layers-related sections
Date: Sun, 25 Mar 2012 17:10:38 -0500	[thread overview]
Message-ID: <cover.1332712914.git.tom.zanussi@intel.com> (raw)

From: Tom Zanussi <tom.zanussi@intel.com>

The BSP Layers section of the BSP Guide contained some example layers
that don't really belong in a generic guide - this patchset removes
them, and updates the related README section.

It also updates the README.sources section, which I noticed shouldn't
really be optional.

The following changes since commit 18c537d96bde8fac7f62071585b71aed05037410:
  Scott Rifenbark (1):
        documentation/poky-ref-manual/development.xml: another env var clarification

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib.git tzanussi/yocto-docs-bsp-layers-updates
  http://git.yoctoproject.org/cgit.cgi//log/?h=tzanussi/yocto-docs-bsp-layers-updates

Tom Zanussi (3):
  documentation/bsp-guide/bsp.xml: remove mention of specific BSPs
  documentation/bsp-guide/bsp.xml: update the README section
  documentation/bsp-guide/bsp.xml: make README.sources non-optional

 documentation/bsp-guide/bsp.xml |   49 ++++++++++++--------------------------
 1 files changed, 16 insertions(+), 33 deletions(-)



             reply	other threads:[~2012-03-25 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-25 22:10 tom.zanussi [this message]
2012-03-25 22:10 ` [PATCH 1/3] documentation/bsp-guide/bsp.xml: remove mention of specific BSPs tom.zanussi
2012-03-25 22:10 ` [PATCH 2/3] documentation/bsp-guide/bsp.xml: update the README section tom.zanussi
2012-03-25 22:10 ` [PATCH 3/3] documentation/bsp-guide/bsp.xml: make README.sources non-optional tom.zanussi

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=cover.1332712914.git.tom.zanussi@intel.com \
    --to=tom.zanussi@intel.com \
    --cc=rpjday@crashcourse.ca \
    --cc=scott.m.rifenbark@intel.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.