Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Chris Larson <clarson@kergoth.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	"bitbake-devel@lists.openembedded.org"
	<bitbake-devel@lists.openembedded.org>,
	Ross Burton <ross.burton@intel.com>
Subject: Re: Some 'depexp' nits
Date: Fri, 08 Nov 2013 05:28:20 -0700	[thread overview]
Message-ID: <527CD8E4.4000202@mlbassoc.com> (raw)
In-Reply-To: <CABcZANkDuRL2bMgoy=zNbguwT6xWXw0ktDhy0KPOMZwAiS4kfg@mail.gmail.com>

On 2013-11-07 09:46, Chris Larson wrote:
>
> On Thu, Nov 7, 2013 at 9:36 AM, Gary Thomas <gary@mlbassoc.com <mailto:gary@mlbassoc.com>> wrote:
>
>     On 2013-11-07 09:25, Paul Eggleton wrote:
>
>         Hi Gary,
>
>         On Thursday 07 November 2013 08:04:47 Gary Thomas wrote:
>
>             I hope this is the correct list.
>
>             I was just using '-u depexp' and noticed a few small things.
>                  $ bitbake my-qt5-image -u depexp
>                  This UI is only compatible with the -g option
>
>             Perhaps this should be worded more strongly, like this?
>                  This UI requires the -g option
>
>
>         Sounds like a good idea yes.
>
>             Also, after running successfully, I closed the window (using
>             the close WM button) and got this:
>                  $ bitbake my-qt5-image -u depexp -g
>                  Unable to cleanly stop: No such command
>
>             There didn't seem to be any other way to exit the program, so
>             at least this should be clean.
>
>
>         There is now a bug open for the latter issue:
>         https://bugzilla.yoctoproject.__org/show_bug.cgi?id=5445 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=5445>
>
>             Are these valid concerns/observations?  Would you entertain patches
>             for these items?
>
>
>         Yes, that would be great.
>
>
>     Can I send them against the Poky/Yocto tree?  Or should it be the
>     separate bitbake tree (which is where?)?
>
>
> http://git.openembedded.org/, mirrored at https://github.com/openembedded/. Submit the patches against the separate bitbake repo to the bitbake-devel list.

I sent a patch, but I never received it from the list although
I can find it in the list archives.  This made me think I had
messed up somehow, so I ended up sending it three times :-(

Did you (or anyone) actually see it?  Did I do something wrong?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2013-11-08 12:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07 15:04 Some 'depexp' nits Gary Thomas
2013-11-07 16:25 ` Paul Eggleton
2013-11-07 16:36   ` Gary Thomas
2013-11-07 16:46     ` Chris Larson
2013-11-08 12:28       ` Gary Thomas [this message]
2013-11-08 12:37         ` Burton, Ross
2013-11-08 13:20           ` Gary Thomas
2013-11-08 13:33             ` Burton, Ross
2013-11-08 17:13             ` 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=527CD8E4.4000202@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=clarson@kergoth.com \
    --cc=paul.eggleton@linux.intel.com \
    --cc=ross.burton@intel.com \
    /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