Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Cristian Iorga <cristian.iorga@intel.com>,
	openembedded-core@lists.openembedded.org
Cc: openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] Cristian Iorga : telepathy-mission-control: upgrade to 5.16.0
Date: Thu, 31 Oct 2013 10:49:10 +0100	[thread overview]
Message-ID: <20131031094910.GH32015@jama> (raw)
In-Reply-To: <20131030171857.47AA3504D1@opal>

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

On Wed, Oct 30, 2013 at 05:18:57PM +0000, git@git.openembedded.org wrote:
> Module: openembedded-core.git
> Branch: master
> Commit: 6bae01a04a375906731555b997766d41f887b496
> URL:    http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=6bae01a04a375906731555b997766d41f887b496
> 
> Author: Cristian Iorga <cristian.iorga@intel.com>
> Date:   Wed Oct 30 10:53:11 2013 +0200
> 
> telepathy-mission-control: upgrade to 5.16.0
> 
> Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
> Signed-off-by: Saul Wold <sgw@linux.intel.com>

Please see Ross's comment in
http://patchwork.openembedded.org/patch/59289/

some PACKAGECONFIGs shouldn't be needed now

> 
> ---
> 
>  ...15.0.bb => telepathy-mission-control_5.16.0.bb} |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/recipes-connectivity/telepathy/telepathy-mission-control_5.15.0.bb b/meta/recipes-connectivity/telepathy/telepathy-mission-control_5.16.0.bb
> similarity index 93%
> rename from meta/recipes-connectivity/telepathy/telepathy-mission-control_5.15.0.bb
> rename to meta/recipes-connectivity/telepathy/telepathy-mission-control_5.16.0.bb
> index f1a1320..bdab9c1 100644
> --- a/meta/recipes-connectivity/telepathy/telepathy-mission-control_5.15.0.bb
> +++ b/meta/recipes-connectivity/telepathy/telepathy-mission-control_5.16.0.bb
> @@ -9,8 +9,8 @@ DEPENDS = "libtelepathy dbus-glib gconf libxslt-native"
>  SRC_URI = "http://telepathy.freedesktop.org/releases/telepathy-mission-control/telepathy-mission-control-${PV}.tar.gz \
>  	file://tmc-Makefile-fix-race.patch \
>  	"
> -SRC_URI[md5sum] = "0efd7d9043f6e189e8ed8111d043b52c"
> -SRC_URI[sha256sum] = "88800d1b5f385e94b34721319ff4fe65c493632954d7229b36e57af5b4a7e1b5"
> +SRC_URI[md5sum] = "736ae9d71028d8e6d95017433c07fa06"
> +SRC_URI[sha256sum] = "edc3c7265c291343d5d7d47c20add4d426e894068c66c79696795502a4e1c1d0"
>  
>  inherit autotools pkgconfig pythonnative
>  
> 
> _______________________________________________
> Openembedded-commits mailing list
> Openembedded-commits@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-commits

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

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

       reply	other threads:[~2013-10-31  9:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20131030171857.47AA3504D1@opal>
2013-10-31  9:49 ` Martin Jansa [this message]
2013-10-31  9:52   ` [oe-commits] Cristian Iorga : telepathy-mission-control: upgrade to 5.16.0 Iorga, Cristian

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=20131031094910.GH32015@jama \
    --to=martin.jansa@gmail.com \
    --cc=cristian.iorga@intel.com \
    --cc=openembedded-commits@lists.openembedded.org \
    --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