Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Dengke Du <dengke.du@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] openssh: Restore TCP wrappers support
Date: Fri, 30 Jun 2017 01:11:44 -0400	[thread overview]
Message-ID: <cover.1498799447.git.dengke.du@windriver.com> (raw)

The following changes since commit 98099349e358a9caaec8ec81f0d4abe588909cfe:

  bitbake: npm fetcher: fix unknown variable name. (2017-06-29 14:33:42 +0100)

are available in the git repository at:

  https://github.com/DengkeDu/openembedded-core.git dengke/openssh-restore-tcp-wrappers-support
  https://github.com//tree/dengke/openssh-restore-tcp-wrappers-support

Wenzong Fan (1):
  openssh: Restore TCP wrappers support

 .../openssh/openssh/restore-tcp-wrappers.patch     | 183 +++++++++++++++++++++
 meta/recipes-connectivity/openssh/openssh_7.5p1.bb |   4 +
 2 files changed, 187 insertions(+)
 create mode 100644 meta/recipes-connectivity/openssh/openssh/restore-tcp-wrappers.patch

-- 
2.8.1



             reply	other threads:[~2017-06-30  5:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-30  5:11 Dengke Du [this message]
2017-06-30  5:11 ` [PATCH 1/1] openssh: Restore TCP wrappers support Dengke Du

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.1498799447.git.dengke.du@windriver.com \
    --to=dengke.du@windriver.com \
    --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