Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Hongxu Jia <hongxu.jia@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] list-packageconfig-flag.py: add a script to list all PACKAGECONFIG's flags
Date: Fri, 02 Aug 2013 11:40:53 +0100	[thread overview]
Message-ID: <2803921.ll8rIZ9yu3@helios> (raw)
In-Reply-To: <51FB83D9.80904@windriver.com>

On Friday 02 August 2013 18:03:05 Hongxu Jia wrote:
> I have updated the pull branch to rename the script and correct the comments
> as your suggestions.

There still seem to be a lot of instances of "PACKAGECONFIG's flags" on the 
branch.

> The suggestion about using bitbake parser to make the script more robust,
> I need some time to do the investigation and I am very pleased to do that,
> I will address this in follow-up pathch, would you think it's proper or not?

Yes, that's fine.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-08-02 10:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-01 11:04 [PATCH 0/1] list-packageconfig-flag.py: add a script to list all PACKAGECONFIG's flags Hongxu Jia
2013-08-01 11:04 ` [PATCH 1/1] " Hongxu Jia
2013-08-01 16:46   ` Otavio Salvador
2013-08-02  1:50     ` Hongxu Jia
2013-08-02  1:54       ` Otavio Salvador
2013-08-02  8:24   ` Paul Eggleton
2013-08-02  9:14     ` Hongxu Jia
2013-08-02 10:38       ` Paul Eggleton
2013-08-02 10:03     ` Hongxu Jia
2013-08-02 10:40       ` Paul Eggleton [this message]
2013-08-03  3:15         ` Hongxu Jia
  -- strict thread matches above, loose matches on Subject: below --
2013-08-02  2:20 [PATCH V2 0/1] " Hongxu Jia
2013-08-02  2:20 ` [PATCH 1/1] " Hongxu Jia

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=2803921.ll8rIZ9yu3@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=hongxu.jia@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox