From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] New recipe - jansson, C library for encoding, decoding and manipulating JSON data
Date: Thu, 12 Apr 2012 16:14:13 +0100 [thread overview]
Message-ID: <4F86F145.5070506@communistcode.co.uk> (raw)
In-Reply-To: <0FAFCFF9-3DB3-46A9-9D7D-078126CCE1C3@dominion.thruhere.net>
On 12/04/12 15:40, Koen Kooi wrote:
> Op 12 apr. 2012, om 16:38 heeft Andreas Oberritter het volgende geschreven:
>
>> On 12.04.2012 16:17, Jack Mitchell wrote:
>>> On 12/04/12 15:08, Koen Kooi wrote:
>>>> Op 12 apr. 2012, om 15:42 heeft ml@communistcode.co.uk het volgende
>>>> geschreven:
>>>>
>>>>> From: Jack Mitchell<jack.mitchell@dbbroadcast.co.uk>
>>>>>
>>>>> Signed-off-by: Jack Mitchell<jack.mitchell@dbbroadcast.co.uk>
>>>>> ---
>>>>> meta-oe/recipes-support/jansson/jansson.inc | 8 ++++++++
>>>>> meta-oe/recipes-support/jansson/jansson_2.3.bb | 4 ++++
>> ^^^^^^^
>>
>>>> I'll ask the standard question: why is this needed in oe-core?
>>>>
>>>> regards,
>>>>
>>>> Koen
>> I think there's a misunderstanding. Jack sent the patch to the wrong list.
>>
>> Jack, patches for meta-oe should be submitted to
>> openembedded-devel@lists.openembedded.org, with [meta-oe] as part of the
>> subject. See http://www.openembedded.org/wiki/Mailing_lists.
> Or read the dang README in the meta-oe layer, it's called README for a reason.
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Apologies. On further inspection it seems openembedded-devel was the
right place to send this patch. I have been under the impression that
oe-core was the new meta-oe & oe-core list and oe-dev was the
maintenance oe-classic list. I followed the Wiki page and made
alterations as I saw fit.
n.b. Koen, whilst I understand that the information was in the README
(which I have now read - thanks) I was following the Wiki and doing what
I believed to be right. It is not a requisite of my job to push patches
back, I was doing it out of support for the community and the drive to
help others. As it was my first ever OE Patch, and therefore my first
offence I don't believe the snarkyness was warranted.
Regards,
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
prev parent reply other threads:[~2012-04-12 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 13:42 [PATCH] New recipe - jansson, C library for encoding, decoding and manipulating JSON data ml
2012-04-12 14:08 ` Koen Kooi
2012-04-12 14:17 ` Jack Mitchell
2012-04-12 14:36 ` Paul Eggleton
2012-04-12 14:38 ` Andreas Oberritter
2012-04-12 14:40 ` Koen Kooi
2012-04-12 15:14 ` Jack Mitchell [this message]
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=4F86F145.5070506@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--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