From: tom.zanussi@intel.com
To: yocto@yoctoproject.org
Subject: [PATCH 00/10] Make dd text in READMEs consistent
Date: Mon, 6 Jan 2014 11:55:29 -0600 [thread overview]
Message-ID: <cover.1389030821.git.tom.zanussi@intel.com> (raw)
From: Tom Zanussi <tom.zanussi@intel.com>
This updates all the top-level meta-intel BSPs with consistent
text for the dd step.
The following changes since commit f707b6c67909ccd84cb2070bdc15777573833461:
meta-fri2: Use the symlink to the actual image in README (2014-01-06 11:34:28 -0600)
are available in the git repository at:
git://git.yoctoproject.org/meta-intel-contrib.git tzanussi/consistify-README-dd-text
http://git.yoctoproject.org/cgit.cgi//log/?h=tzanussi/consistify-README-dd-text
Tom Zanussi (10):
meta-chiefriver: Use the symlink to the actual image in README
meta-crownbay: Use the symlink to the actual image in README
meta-crystalforest: Use the symlink to the actual image in README
meta-emenlow: Use the symlink to the actual image in README
meta-jasperforest: Use the symlink to the actual image in README
meta-n450: Use the symlink to the actual image in README
meta-nuc: Use the symlink to the actual image in README
meta-romley: Use the symlink to the actual image in README
meta-sugarbay: Use the symlink to the actual image in README
meta-sys940x: Use the symlink to the actual image in README
meta-chiefriver/README | 2 +-
meta-crownbay/README | 2 +-
meta-crystalforest/README | 4 ++--
meta-emenlow/README | 2 +-
meta-jasperforest/README | 2 +-
meta-n450/README | 2 +-
meta-nuc/README | 2 +-
meta-romley/README | 2 +-
meta-sugarbay/README | 2 +-
meta-sys940x/README | 2 +-
10 files changed, 11 insertions(+), 11 deletions(-)
--
1.7.9.5
next reply other threads:[~2014-01-06 16:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 17:55 tom.zanussi [this message]
2014-01-06 16:54 ` [PATCH 00/10] Make dd text in READMEs consistent Tom Zanussi
2014-01-06 17:55 ` [PATCH 01/10] meta-chiefriver: Use the symlink to the actual image in README tom.zanussi
2014-01-06 17:55 ` [PATCH 02/10] meta-crownbay: " tom.zanussi
2014-01-06 17:55 ` [PATCH 03/10] meta-crystalforest: " tom.zanussi
2014-01-06 17:55 ` [PATCH 04/10] meta-emenlow: " tom.zanussi
2014-01-06 17:55 ` [PATCH 05/10] meta-jasperforest: " tom.zanussi
2014-01-06 17:55 ` [PATCH 06/10] meta-n450: " tom.zanussi
2014-01-06 17:55 ` [PATCH 07/10] meta-nuc: " tom.zanussi
2014-01-06 17:55 ` [PATCH 08/10] meta-romley: " tom.zanussi
2014-01-06 17:55 ` [PATCH 09/10] meta-sugarbay: " tom.zanussi
2014-01-06 17:55 ` [PATCH 10/10] meta-sys940x: " 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.1389030821.git.tom.zanussi@intel.com \
--to=tom.zanussi@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.