public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Maxin B. John" <maxin.john@intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/4] gstreamer1.0-omx: provide RECIPE_NO_UPDATE_REASON
Date: Fri, 9 Sep 2016 10:42:14 +0300	[thread overview]
Message-ID: <20160909074213.GA5638@mbabyjoh-desk.ger.corp.intel.com> (raw)
In-Reply-To: <CAJTo0LZOm52gsC7LgcJkdDA6Hsq3V3n29o4n8vqPvwW+DhjUDw@mail.gmail.com>

Hi Ross,

>On Thu, Sep 08, 2016 at 05:04:26PM +0100, Burton, Ross wrote:
>>On 8 September 2016 at 16:46, Maxin B. John <maxin.john@intel.com> wrote:
>>
>>   +RECIPE_NO_UPDATE_REASON = "Version 1.9.2 requires gstreamer-1.0 >= 1.9.2"
>
>Are they adopting the GStreamer versioning style, so we should inherit upstream-version-is-even instead?
>

The number of gstreamer-1.0-omx releases seems to be pretty small compared
to other components of the gstreamer project. Seems like they are moving to
the GStreamer versioning style recently. 

I will update this as per your suggestion.

>   Ross

Thanks,
Maxin


      reply	other threads:[~2016-09-09  7:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08 15:46 [PATCH 1/4] gstreamer1.0-omx: provide RECIPE_NO_UPDATE_REASON Maxin B. John
2016-09-08 15:46 ` [PATCH 2/4] kmod: inherit pkgconfig Maxin B. John
2016-09-08 15:46 ` [PATCH 3/4] kconfig-frontends: " Maxin B. John
2016-09-08 15:46 ` [PATCH 4/4] libical: fix build failure after changing machine Maxin B. John
2016-09-08 16:04 ` [PATCH 1/4] gstreamer1.0-omx: provide RECIPE_NO_UPDATE_REASON Burton, Ross
2016-09-09  7:42   ` Maxin B. John [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=20160909074213.GA5638@mbabyjoh-desk.ger.corp.intel.com \
    --to=maxin.john@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox