Openembedded Core Discussions
 help / color / mirror / Atom feed
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 15:17:35 +0100	[thread overview]
Message-ID: <4F86E3FF.3050905@communistcode.co.uk> (raw)
In-Reply-To: <2244DB0D-6E70-4128-BBBA-EFABB2C489EE@dominion.thruhere.net>

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
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

It was in oe-classic so I believed it would be useful to port it over 
oe-core. I thought that the location I chose was the most suitable place 
for it. There doesn't seem to be a general 'user-cotrib/devel' layer 
into which these packages can go, I was unsure of it's relevance but a 
patch declined is a patch archived, right?

Kind Regards,

-- 

   Jack Mitchell (jack@embed.me.uk)
   Embedded Systems Engineer
   http://www.embed.me.uk

--




  reply	other threads:[~2012-04-12 14:26 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 [this message]
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

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=4F86E3FF.3050905@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