From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] [meta-oe] giflib: Move to OE-Core
Date: Thu, 22 Mar 2012 12:28:04 +0100 [thread overview]
Message-ID: <jkf2bu$9pb$1@dough.gmane.org> (raw)
In-Reply-To: <CAGiJk9cUPhrLHQicRsDfa-e_vn=0OdmE=BuyXxvi7cJX1XUfrw@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 22-03-12 11:12, Samuel Stirtzel schreef:
> 2012/3/22 Eric Bénard <eric@eukrea.com>:
>> Le Thu, 22 Mar 2012 10:35:31 +0100, Samuel Stirtzel
>> <s.stirtzel@googlemail.com> a écrit :
>>> 2012/3/22 Martin Jansa <martin.jansa@gmail.com>:
>>>> why not add meta-oe dependency to meta-kde/README?
>>>
>>> It is already listed as dependency [1]. But somehow it seems like
>>> that there are users, interested in testing this layer, with an use
>>> case which excludes the meta-oe layer.
>>>
>>>
>> can you describe this use case so that meta-oe gets a chance to adapt.
>
> Since I have the common use case of the installation provided from the
> setup-scripts and I don't know the exact use case, I cannot provide this
> information myself right now.
So you can't explain why it should move to oe-core, that should be enough to
NAK this patch without even looking at it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org
iQIcBAEBAgAGBQJPawy/AAoJEHZqAkdh1vT6cdAP/3CIpSE6k6BOPHXEri6hgLU4
kfQhs6GKHRxgyCB63jDWJ1EShrErKUrCksWMAXO6p7tBniuMk8X5mJmQ4mBfHH9b
0yTu5bPFxB/zsK0lFqoOfWMOuwaJLZJQCuEQLJP4VvlVxexb5sZMbzMvudh+pGwQ
DZEgDGbTF+hUrcxu0Rjxug9UXJa4nqfiCJ7ShKy3U2+ichZnr4tU9YfUl5ZGoofT
W/xtJOBwEKogGB0KxIb2tphtChpoA8rPMy5WvRqlJ39lDsUOdOHUl5/Vu83Czpee
ynFe5aRxYjsz0NUovuiBc5SUwVCwqJApR164FCFIkhHg7l1G7OJelSrn1+oqA62f
fX6MTno5dYpaWImx2KiGqHOKqJF4wo+C0QqGNFBYde4Yu9Xu2Wdx/GQnycov6TOf
deQtQnDHFZ4K4oaT4ptQvzcb0qN4KU5f3scCjSAR9SMNfPjjuaI7wmlRD8UwGB61
s1oipV+SNE9icv8qSGbV9gw1Bo+B9w4AHRZllt9tdsDhnoMldBot7Fhc+FuW0MbH
uFOmzi4R1j9lXmoh5pcFkmZKSYra4/UhU9DkwGZ4IZzEMCE4cxfwDc3MYGyPPOTE
0oMbq01pmAfPsio7gQ1bE73WC0JWBhKfbFJ7KxF3mH0oC1+mrBw9y2Al+7Zd0o7P
B+y8ooG5B0ELZdWvczXO
=EYSh
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-03-22 11:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 14:17 [PATCH] [meta-oe] giflib: Move to OE-Core Samuel Stirtzel
2012-03-21 14:21 ` Samuel Stirtzel
2012-03-21 21:09 ` Koen Kooi
2012-03-22 9:24 ` Samuel Stirtzel
2012-03-22 9:28 ` Martin Jansa
2012-03-22 9:35 ` Samuel Stirtzel
2012-03-22 9:40 ` Eric Bénard
2012-03-22 9:42 ` Koen Kooi
2012-03-22 9:45 ` Eric Bénard
2012-03-22 10:02 ` Koen Kooi
2012-03-22 16:04 ` Khem Raj
2012-03-22 10:12 ` Samuel Stirtzel
2012-03-22 11:28 ` Koen Kooi [this message]
2012-03-22 11:38 ` Samuel Stirtzel
2012-03-22 12:10 ` Koen Kooi
2012-03-22 12:36 ` Samuel Stirtzel
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='jkf2bu$9pb$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@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