All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: "Chang, Rebecca Swee Fun" <rebecca.swee.fun.chang@intel.com>
Cc: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe] [jethro] Additional version supported in stable branch
Date: Wed, 9 Mar 2016 13:09:34 +0100	[thread overview]
Message-ID: <20160309120934.GA2542@jama> (raw)
In-Reply-To: <50B33AC5ED75F74F991980326F1C438D191C80FE@PGSMSX103.gar.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]

On Wed, Mar 09, 2016 at 03:22:47AM +0000, Chang, Rebecca Swee Fun wrote:
> Dear maintainers,
> 
> I would like to collect inputs from all of you whether is it possible to have 2 versions of libvpx supported in Jethro branch.
> 
> I have recently submitted libvpx v1.5 upgrade to master branch. I do understand that stable branch is mainly used for security updates/fixes.
> So this is why I'm proposing to support 2 versions instead of upgrading in Jethro.
> 
> The reason behind is, we are enabling video decode/encode feature to customers but our target BSP components are still based on Jethro.

Then backport the newer version on your layer.

> Please let me know your concern whether this is feasible. Thank you very much.

We also backport newer versions for various components, we even have
separate layers for backports from various Yocto releases (so that whole
layer can be dropped when upgrading to newer release without functional
changes in backported recipes).

Doing it in upstream layers would cause unnecessary changes to everybody
else.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

      parent reply	other threads:[~2016-03-09 12:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09  3:22 [meta-oe] [jethro] Additional version supported in stable branch Chang, Rebecca Swee Fun
2016-03-09  4:08 ` Khem Raj
2016-03-09 12:09 ` 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=20160309120934.GA2542@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=rebecca.swee.fun.chang@intel.com \
    /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.