Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: andreas.kling@gmail.com
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-gnome][PATCH v02 3/3] dconf: make gtk+3 dependency optional
Date: Fri, 10 Feb 2017 10:07:19 +0100	[thread overview]
Message-ID: <20170210090722.11753-1-andreas.kling@gmail.com> (raw)
In-Reply-To: <CALbNGRQAEX5aBsvsb3rY3CQ1C0V-WFzsJKxnNnLos8LdJJxA9g@mail.gmail.com>

many thanks for your review.
no idea how I only recognized rdepends in base class.

v03
remove duplicated depends to gtk+3
rebase from master to master-next

v02
fix typo

[oe] [meta-gnome][PATCH v03 1/3] dconf: depends on dbus
[oe] [meta-gnome][PATCH v03 2/3] dconf: fix bash completion in wrong
[oe] [meta-gnome][PATCH v03 3/3] dconf: make gtk+3 dependency


  reply	other threads:[~2017-02-10  9:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08 14:07 dconf: conditionally depend on gtk+3 andreas.kling
2017-02-08 14:07 ` [meta-gnome][PATCH 1/3] dconf: depends on dbus andreas.kling
2017-02-08 14:07 ` [meta-gnome][PATCH 2/3] dconf: fix bash completion in wrong package andreas.kling
2017-02-08 14:07 ` [meta-gnome][PATCH 3/3] dconf: make gtk+3 dependency optional andreas.kling
2017-02-08 14:31 ` dconf: conditionally depend on gtk+3 andreas.kling
2017-02-08 14:31   ` [meta-gnome][PATCH v02 1/3] dconf: depends on dbus andreas.kling
2017-02-08 14:31   ` [meta-gnome][PATCH v02 2/3] dconf: fix bash completion in wrong package andreas.kling
2017-02-08 14:31   ` [meta-gnome][PATCH v02 3/3] dconf: make gtk+3 dependency optional andreas.kling
2017-02-08 15:08     ` Andreas Müller
2017-02-10  9:07       ` andreas.kling [this message]
2017-02-10  9:07         ` [meta-gnome][PATCH v03 1/3] dconf: depends on dbus andreas.kling
2017-02-10  9:07         ` [meta-gnome][PATCH v03 2/3] dconf: fix bash completion in wrong package andreas.kling
2017-02-10  9:07         ` [meta-gnome][PATCH v03 3/3] dconf: make gtk+3 dependency optional andreas.kling

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=20170210090722.11753-1-andreas.kling@gmail.com \
    --to=andreas.kling@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