From: Tom Zanussi <tom.zanussi@intel.com>
To: nitin.a.kamble@intel.com
Cc: yocto@yoctoproject.org, darren.hart@intel.com
Subject: Re: [PATCH v2 2/6] chiefriver: add WEBTITLE & Compliance information
Date: Wed, 24 Oct 2012 19:14:58 -0500 [thread overview]
Message-ID: <1351124098.27553.55.camel@empanada> (raw)
In-Reply-To: <f1a7d9cde11e622392859625fed95edde1a28db5.1351110208.git.nitin.a.kamble@intel.com>
On Wed, 2012-10-24 at 13:25 -0700, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble <nitin.a.kamble@intel.com>
>
> The WEBTITLE will be used to publish the BSP on the Yocto Project Website.
> And adding the Yocto Project Compliance information for the 1.3 release.
> Also specifying all the layers used from meta-intel repository.
>
> Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> ---
> meta-chiefriver/README | 8 +++++++-
> meta-chiefriver/conf/machine/chiefriver.conf | 2 ++
> 2 files changed, 9 insertions(+), 1 deletions(-)
>
> diff --git a/meta-chiefriver/README b/meta-chiefriver/README
> index 7c47b02..249a389 100644
> --- a/meta-chiefriver/README
> +++ b/meta-chiefriver/README
> @@ -7,6 +7,12 @@ plus the Panther Point PCH. This BSP assumes that the Ivy Bridge
> integrated graphics are being used.
>
>
> +Compliance
> +==========
> +This BSP is compliant with Yocto Project as per requirements listed here:
> +http://www.yoctoproject.org/yocto-project-compatible-registration
> +
To be consistent with the rest of the README, there should be a blank
line between the ===== and the 'This BSP... ' text.
Also, for readability, it would be nice to have the URL also separated
by a blank line from the preceding text, and indented a couple spaces
like similar lines in the README.
Also, I think the compliance text reads better as:
This BSP is compliant with the Yocto Project as per the requirements
listed here:
> +
> Dependencies
> ============
>
> @@ -20,7 +26,7 @@ This layer depends on:
> branch: master
>
> URI: git://git.yoctoproject.org/meta-intel
> - layers: intel
> + layers: meta-intel, meta-chiefriver
If you look at the meta-intel/conf/layer.conf, you see the layer
actually is 'intel'.
Also, this is the README for the chiefriver layer, so it can't depend on
itself i.e. meta-chiefriver or 'chiefriver' shouldn't be listed in
layers
> branch: master
>
>
> diff --git a/meta-chiefriver/conf/machine/chiefriver.conf b/meta-chiefriver/conf/machine/chiefriver.conf
> index b8b8754..5005ce0 100644
> --- a/meta-chiefriver/conf/machine/chiefriver.conf
> +++ b/meta-chiefriver/conf/machine/chiefriver.conf
> @@ -1,6 +1,8 @@
> #@TYPE: Machine
> #@NAME: chiefriver
>
> +#@WEBTITLE: Intel 3rd Generations Core Platforms: Core i3, i5, i7 (Ivy Bridge)
> +
Since this is text that will appear on the website, we need to be a
little picky about grammar: it should read '3rd Generation' rather than
'3rd Generations'
These comments apply to the other README files as well, so I won't
repeat them there, other than to fix any text that might appear on the
website for those as well...
Tom
> #@DESCRIPTION: Machine configuration for Chief River systems
> # i.e. Ivy Bridge + Panther Point
>
next prev parent reply other threads:[~2012-10-25 0:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 20:25 [PATCH v2 0/6] meta-intel: README updates nitin.a.kamble
2012-10-24 20:25 ` [PATCH v2 1/6] MAINTAINERS: correct pathname nitin.a.kamble
2012-10-24 20:25 ` [PATCH v2 2/6] chiefriver: add WEBTITLE & Compliance information nitin.a.kamble
2012-10-25 0:14 ` Tom Zanussi [this message]
2012-10-25 17:00 ` Kamble, Nitin A
2012-10-25 17:13 ` Kamble, Nitin A
2012-10-24 20:25 ` [PATCH v2 3/6] crownbay: " nitin.a.kamble
2012-10-25 0:30 ` Tom Zanussi
2012-10-24 20:25 ` [PATCH v2 4/6] emenlow: " nitin.a.kamble
2012-10-25 0:32 ` Tom Zanussi
2012-10-24 20:25 ` [PATCH v2 5/6] jasperforest: " nitin.a.kamble
2012-10-25 0:34 ` Tom Zanussi
2012-10-24 20:25 ` [PATCH v2 6/6] sugarbay: " nitin.a.kamble
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=1351124098.27553.55.camel@empanada \
--to=tom.zanussi@intel.com \
--cc=darren.hart@intel.com \
--cc=nitin.a.kamble@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.