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 13:10:13 +0100 [thread overview]
Message-ID: <jkf4r1$u81$1@dough.gmane.org> (raw)
In-Reply-To: <CAGiJk9fXnA24HKjF9rkhkoimDO1etb9eEExNG1Div1bze=XQSA@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 22-03-12 12:38, Samuel Stirtzel schreef:
> 2012/3/22 Koen Kooi <koen@dominion.thruhere.net>: 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.
>
>> If the explanation that an user group that has another use case
No, an *alledged* user group that *might* have an *alledged* use case for
which you say yourself you cannot provide the information. That is what I'm
complaining about, the degrees of hearsay and hypotheticals in your argument.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org
iQIcBAEBAgAGBQJPaxajAAoJEHZqAkdh1vT6+PgP/13/oayQIuLVdpEx2uslB0LZ
XV5ctwGBoPW6VCIXg/GpTe0BzdIe8hUdnCLZt0gLf2UMN44Wy3RNVZ86000s0GM3
R1/cJ+qNCjrjvNQtUYazG5fklvOk1MtHQnhvyznmkhrSYdaPsMQeeZHkdGey35X6
MZavWe0ufOdKwJG7xgRb5LETduk8IgK6l7sYXr8lIvqq+TRzOqwkDO8ny1cQz1O6
yKFPDisAQGsn4IKwwxPnpoS9/78y8HK4oo6jq5KWoLkQHIGmqe224mTTv7F+EV0b
Ph/TwCQO6oNFLj64oaW9lQpBO1sSTBAMj51Oxvs8cHdQsZeswiAYH9qm8rbrNlRy
QM0QRPxx6aB1K242ZcQfAlMXjgiw0akiMxtxMknJJTzVIpXINV+ZLn2TxsRVHRh+
buuL7HCOiwGYXXzheXLaX4fS+Ctf4i6y0oI8o1F3vscAcj5z7n0YCEG0xu4wWddd
bVbKQ/NHAnkdEE2PKYoP3jJirzFAfh/1X2NCWgD0CJSYoNkukZ3Tx1reINHg4mW5
r3pFkaxo3B/5QaEHgo6Q8w/bGHu6toOjc3xt7yZPVp1Ita8yRxFEulrBcecd+UbO
zzorKmBkJ96y98C6q2ihbo+SqrCGn/5Sx1b/8y7r70DWXyuECasdWM+5ASBmiiJs
TAl4oHGfVVoedxmuD7fJ
=AxKX
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-03-22 12:19 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
2012-03-22 11:38 ` Samuel Stirtzel
2012-03-22 12:10 ` Koen Kooi [this message]
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='jkf4r1$u81$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