Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 0/2] avoid nautilus build by default
Date: Sun, 20 Apr 2014 13:49:45 +0200	[thread overview]
Message-ID: <20140420114945.GG2486@jama> (raw)
In-Reply-To: <1397633550-19323-1-git-send-email-schnitzeltony@googlemail.com>

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

On Wed, Apr 16, 2014 at 09:32:28AM +0200, Andreas Müller wrote:
> There is no reason why we need to build nautilus when using evince and/or
> gnome-disk-utility.

Both merged, thanks!

> 
> Andreas Müller (2):
>   evince: make nautilus extension a PACKAGECONFIG and disable by default
>   gnome-disk-utility: change PACKAGECONFIG default: remove nautilus
> 
>  meta-gnome/recipes-gnome/evince/evince_2.32.0.bb                    | 6 ++++--
>  .../recipes-gnome/gnome-disk-utility/gnome-disk-utility_2.32.0.bb   | 4 ++--
>  2 files changed, 6 insertions(+), 4 deletions(-)
> 
> -- 
> 1.8.3.1
> 
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

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

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

      parent reply	other threads:[~2014-04-20 11:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16  7:32 [PATCH 0/2] avoid nautilus build by default Andreas Müller
2014-04-16  7:32 ` [PATCH 1/2] evince: make nautilus extension a PACKAGECONFIG and disable " Andreas Müller
2014-04-16  7:32 ` [PATCH 2/2] gnome-disk-utility: change PACKAGECONFIG default: remove nautilus Andreas Müller
2014-04-20 11:49 ` 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=20140420114945.GG2486@jama \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox