All of lore.kernel.org
 help / color / mirror / Atom feed
From: Armin Kuster <akuster808@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [PATCH 0/6] thud patch review
Date: Sun, 24 Mar 2019 18:52:54 -0700	[thread overview]
Message-ID: <cover.1553478496.git.akuster808@gmail.com> (raw)

Please review and provide feedback no later than Tuesday March 26 18:00 pst

The following changes since commit 6ef9657068492d4644079c88f2adee9c3cac9543:

  vim: improve reproducibility (2019-02-04 22:09:31 -0800)

are available in the git repository at:

  git://git.openembedded.org/meta-openembedded-contrib stable/thud-next
  http://cgit.openembedded.org/meta-openembedded-contrib/log/?h=stable/thud-next

Adrian Bunk (2):
  wireless-regdb: update 2018.05.31 -> 2018.10.24
  Split ntpq into an own package

André Draszik (2):
  mosquitto: fix build in systemd environments
  mosquitto: fully switch over to using PACKAGECONFIG_CONFARGS

Khem Raj (1):
  rtmpdump: Switch to using GNU TLS instead of openssl10

Ovidiu Panait (1):
  python3-blivetgui: Fix _supported_filesystems crash

 .../recipes-multimedia/rtmpdump/rtmpdump_2.4.bb    |  4 +--
 .../mosquitto/mosquitto_1.5.1.bb                   | 13 +++-----
 ..._2018.05.31.bb => wireless-regdb_2018.10.24.bb} |  4 +--
 .../recipes-support/ntp/ntp_4.2.8p12.bb            |  5 ++-
 ...ted_filesystems-in-BlivetGUIAnaconda-init.patch | 39 ++++++++++++++++++++++
 .../python-blivet/python3-blivetgui_2.1.8.bb       |  1 +
 6 files changed, 53 insertions(+), 13 deletions(-)
 rename meta-networking/recipes-connectivity/wireless-regdb/{wireless-regdb_2018.05.31.bb => wireless-regdb_2018.10.24.bb} (91%)
 create mode 100644 meta-python/recipes-extended/python-blivet/python3-blivetgui/0001-Set-_supported_filesystems-in-BlivetGUIAnaconda-init.patch

-- 
2.7.4



                 reply	other threads:[~2019-03-25  1:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=cover.1553478496.git.akuster808@gmail.com \
    --to=akuster808@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.