From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: finding mime-support in multiple oe trees?
Date: Fri, 11 May 2012 15:37:25 +0200 [thread overview]
Message-ID: <20120511133724.GD3166@jama.jama.net> (raw)
In-Reply-To: <4FAD09FE.4040101@mindchasers.com>
[-- Attachment #1: Type: text/plain, Size: 631 bytes --]
On Fri, May 11, 2012 at 08:45:50AM -0400, Bob Cochran wrote:
> Hello,
>
> I can find recipes for mime-support in both meta-openembedded and
> meta-openembedded-contrib under meta-oe/recipes-support. The former has
> a 3.48 recipe and the latter has a 3.44 recipe.
meta-openembedded-contrib is used for pushing stuff by developers which
then send pull request to pull it to main meta-openembedded repo.
So it's normal that meta-openembedded-contrib has sometimes some newer
stuff and then the branches are not updated anymore and gets old.
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2012-05-11 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 12:45 finding mime-support in multiple oe trees? Bob Cochran
2012-05-11 13:36 ` Paul Eggleton
2012-05-11 13:37 ` Martin Jansa [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=20120511133724.GD3166@jama.jama.net \
--to=martin.jansa@gmail.com \
--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 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.