All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] [RESEND]Create a script for SUMMARY audit in recipes
Date: Tue, 20 Dec 2011 21:45:25 -0800	[thread overview]
Message-ID: <4EF17275.6080202@linux.intel.com> (raw)
In-Reply-To: <cover.1324441819.git.shane.wang@intel.com>

On 12/20/2011 08:32 PM, Shane Wang wrote:
> Here is the script to check which recipe provides SUMMARY and which doesnot.
> For those which do not, maintainer should add or update to a meaningful summary for HOB to display in description.
>
Shane,

I guess I am not understanding why this is needed.  Why can't we use 
DESCRIPTION which is a required entry?  Use the first X Characters of 
DESCRIPTION?

Sau!


> The following changes since commit b281fd127bac9ba77ab63a5c2b812ddd5d56df37:
>
>    documentation/poky-ref-manual/technical-details.xml: edits per Richard Purdie (2011-12-16 16:58:41 +0000)
>
> are available in the git repository at:
>    git://git.pokylinux.org/poky-contrib shane/summary-audit
>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=shane/summary-audit
>
> Shane Wang (1):
>    Create a script for SUMMARY audit in recipes
>
>   scripts/contrib/summary-audit.sh |   55 ++++++++++++++++++++++++++++++++++++++
>   1 files changed, 55 insertions(+), 0 deletions(-)
>   create mode 100755 scripts/contrib/summary-audit.sh
>



  parent reply	other threads:[~2011-12-21  5:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-21  4:32 [PATCH 0/1] [RESEND]Create a script for SUMMARY audit in recipes Shane Wang
2011-12-21  4:32 ` [PATCH 1/1] Create " Shane Wang
2011-12-21  5:45 ` Saul Wold [this message]
2011-12-21  6:10   ` [PATCH 0/1] [RESEND]Create " Wang, Shane
2011-12-21 18:16     ` Joshua Lock
2011-12-21 18:43       ` Saul Wold
2011-12-21 18:59         ` Mark Hatle
2011-12-22 10:17           ` Paul Eggleton

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=4EF17275.6080202@linux.intel.com \
    --to=sgw@linux.intel.com \
    --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 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.