Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Mike Westerhof <mike@mwester.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 3/4] slugos: Pin gvfs to 1.6.6
Date: Mon, 21 Feb 2011 19:22:25 -0600	[thread overview]
Message-ID: <4D630FD1.10205@mwester.net> (raw)
In-Reply-To: <1298214559-9650-4-git-send-email-tom_rini@mentor.com>

On 2/20/2011 9:09 AM, Tom Rini wrote:
> We're doing this since glib-2.0 is pinned.
> 
> Signed-off-by: Tom Rini <tom_rini@mentor.com>

Acked-by: Mike Westerhof <mike@mwester.net>

> ---
>  conf/distro/include/preferred-slugos-versions.inc |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/conf/distro/include/preferred-slugos-versions.inc b/conf/distro/include/preferred-slugos-versions.inc
> index cde3eb0..4f1033c 100644
> --- a/conf/distro/include/preferred-slugos-versions.inc
> +++ b/conf/distro/include/preferred-slugos-versions.inc
> @@ -32,6 +32,7 @@ PREFERRED_VERSION_glib-2.0			?= "2.26.1"
>  PREFERRED_VERSION_glib-2.0-native		?= "2.26.1"
>  PREFERRED_VERSION_gtk+				?= "2.18.6"
>  PREFERRED_VERSION_gtk+-native			?= "2.18.6"
> +PREFERRED_VERSION_gvfs				?= "1.6.6"
>  PREFERRED_VERSION_ipkg				?= "0.99.163"
>  PREFERRED_VERSION_ipkg-native			?= "0.99.163"
>  PREFERRED_VERSION_linux-libc-headers		?= "2.6.31"




  reply	other threads:[~2011-02-22  1:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-20 15:09 [PATCH 0/4] Pin gvfs before making 1.7.2 default Tom Rini
2011-02-20 15:09 ` [PATCH 1/4] angstrom-2008: Pin gvfs at 1.6.6 Tom Rini
2011-02-20 15:20   ` Koen Kooi
2011-02-20 15:09 ` [PATCH 2/4] kaeilos 2009: Pin gvfs to 1.6.6 Tom Rini
2011-05-12  8:23   ` Marco Cavallini
2011-02-20 15:09 ` [PATCH 3/4] slugos: " Tom Rini
2011-02-22  1:22   ` Mike Westerhof [this message]
2011-02-20 15:09 ` [PATCH 4/4] gvfs 1.7.2: Drop DEFAULT_PREFERENCE Tom Rini
2011-02-20 15:19 ` [PATCH 0/4] Pin gvfs before making 1.7.2 default Koen Kooi
2011-02-20 21:56   ` Tom Rini

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=4D630FD1.10205@mwester.net \
    --to=mike@mwester.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox