From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Marek Vasut <marex@denx.de>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Yocto: Install full set of python modules in Qt SDK toolchain
Date: Mon, 11 Aug 2014 11:26:34 +0100 [thread overview]
Message-ID: <1407752794.22187.3.camel@ted> (raw)
In-Reply-To: <201408081422.19749.marex@denx.de>
On Fri, 2014-08-08 at 14:22 +0200, Marek Vasut wrote:
> On Friday, August 08, 2014 at 07:22:04 AM, Koen Kooi wrote:
> > Since 'yocto' is a project like freedesktop.org your commit message doesn't
> > make sense, it should be something like:
> >
> > meta-toolchain-qt: Install full set of python modules
>
> Got it, Saul also told me so. I will wait a bit for some more feedback and
> repost with corrections, OK ? Is this approach I took here even correct please ?
I'd really like to see a packagegroup defined somewhere with this list
of python modules which the various recipes can then reference...
Cheers,
Richard
next prev parent reply other threads:[~2014-08-11 10:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 19:10 [PATCH] Yocto: Install full set of python modules in Qt SDK toolchain Marek Vasut
2014-08-08 5:22 ` Koen Kooi
2014-08-08 12:22 ` Marek Vasut
2014-08-11 10:26 ` Richard Purdie [this message]
2014-08-11 18:26 ` Marek Vasut
2014-09-18 9:11 ` Laszlo Papp
2014-09-18 9:12 ` Laszlo Papp
2014-09-18 9:16 ` Marek Vasut
2014-09-18 9:23 ` Laszlo Papp
2014-09-18 9:30 ` Marek Vasut
2014-09-18 10:29 ` Laszlo Papp
2014-09-18 13:36 ` Richard Purdie
2014-09-19 7:14 ` Marek Vasut
2014-09-19 7:25 ` Richard Purdie
2014-09-21 16:02 ` Marek Vasut
2014-11-27 18:07 ` Laszlo Papp
2014-12-01 15:05 ` Burton, Ross
2014-12-01 15:13 ` Richard Purdie
2014-12-01 15:20 ` Burton, Ross
2014-12-01 15:21 ` Paul Eggleton
2014-12-01 16:44 ` Burton, Ross
2014-12-01 18:04 ` Laszlo Papp
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=1407752794.22187.3.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--cc=marex@denx.de \
--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.