From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] core-image-foo: add summary to each image bb file
Date: Thu, 19 Jan 2012 12:56:28 +0000 [thread overview]
Message-ID: <1326977788.2511.60.camel@ted> (raw)
In-Reply-To: <09ab90b65169616911ae3811421b374158b6453d.1326976547.git.shane.wang@intel.com>
Hi Shane,
On Thu, 2012-01-19 at 20:38 +0800, Shane Wang wrote:
> Add SUMMARY to each image bb file according to poky reference manual for Hob2 use later.
I think this is good but shouldn't some of these be DESCRIPTIONs? The
difference is that summary should be a one line summary (~max 72 chars)
whilst DESCRIPTION can be multiple lines of text...
Cheers,
Richard
next prev parent reply other threads:[~2012-01-19 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 12:38 [PATCH 0/1] core-image-foo: add summary to each image bb file Shane Wang
2012-01-19 12:38 ` [PATCH 1/1] " Shane Wang
2012-01-19 12:56 ` Richard Purdie [this message]
2012-01-19 13:12 ` Wang, Shane
2012-01-19 14:30 ` Richard Purdie
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=1326977788.2511.60.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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