All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1] [RESEND]Create a script for SUMMARY audit in recipes
Date: Wed, 21 Dec 2011 10:16:19 -0800	[thread overview]
Message-ID: <4EF22273.3000007@linux.intel.com> (raw)
In-Reply-To: <D5AB6E638E5A3E4B8F4406B113A5A19A12ED757FB6@shsmsx501.ccr.corp.intel.com>

On 20/12/11 22:10, Wang, Shane wrote:
> Saul Wold wrote on 2011-12-21:
> 
>> 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?

There's a huge difference between a purposefully crafted 72 character
summary and a free-for all description field that will have to be
chopped to be displayed in the GUI. I originally chose summary as a
succinct 72 characters would fit much better in the available UI.

Aside: according to the Yocto docs the SUMMARY field should fall back to
DESCRIPTION anyway. It's just that right now we do that at the package
back-end level for each package back-end.


> OK, then HOB has a bug. To use DESCRIPTION instead of SUMMARY. I am OK with that.
> Josh, Dongxiao, did you see any problem if I change that?

I think it's the wrong solution.

Joshua
-- 
Joshua Lock
        Yocto Project "Johannes factotum"
        Intel Open Source Technology Centre



  reply	other threads:[~2011-12-21 18:23 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 ` [PATCH 0/1] [RESEND]Create " Saul Wold
2011-12-21  6:10   ` Wang, Shane
2011-12-21 18:16     ` Joshua Lock [this message]
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=4EF22273.3000007@linux.intel.com \
    --to=josh@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.