All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Qi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH V3 0/5] systemd misc fixes
Date: Mon, 20 Jan 2014 10:22:58 +0800	[thread overview]
Message-ID: <cover.1390184362.git.Qi.Chen@windriver.com> (raw)

Changes since V2:
1. Recommend the 'less' package instead of depend on it.

The following changes since commit 8163854adf87ac42a8f08ee25685d0ce1efb4724:

  oe-selftest: separated the SStateBase and SStateTests in different modules (2014-01-16 12:18:44 +0000)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib ChenQi/systemd-misc-fixes2
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/systemd-misc-fixes2

Chen Qi (5):
  systemd: add 'less' to its RRECOMMENDS
  dropbear: add systemd unit files
  openssh: fixes for systemd
  distcc: add systemd support
  at: add systemd support

 .../openssh/openssh-6.4p1/sshd.socket              |    1 -
 .../openssh/openssh-6.4p1/sshd@.service            |    1 +
 .../openssh/openssh-6.4p1/sshdgenkeys.service      |    8 ++++----
 meta/recipes-connectivity/openssh/openssh_6.4p1.bb |    4 ++--
 meta/recipes-core/dropbear/dropbear.inc            |   17 ++++++++++++++++-
 .../recipes-core/dropbear/dropbear/dropbear.socket |   10 ++++++++++
 .../dropbear/dropbear/dropbear@.service            |   11 +++++++++++
 .../dropbear/dropbear/dropbearkey.service          |    8 ++++++++
 meta/recipes-core/systemd/systemd_208.bb           |    2 ++
 meta/recipes-devtools/distcc/distcc_3.1.bb         |   14 +++++++++++---
 meta/recipes-devtools/distcc/files/default         |    5 +++++
 meta/recipes-devtools/distcc/files/distccd.service |   11 +++++++++++
 meta/recipes-extended/at/at_3.1.14.bb              |   10 +++++++++-
 meta/recipes-extended/at/files/atd.service         |    9 +++++++++
 14 files changed, 99 insertions(+), 12 deletions(-)
 create mode 100644 meta/recipes-core/dropbear/dropbear/dropbear.socket
 create mode 100644 meta/recipes-core/dropbear/dropbear/dropbear@.service
 create mode 100644 meta/recipes-core/dropbear/dropbear/dropbearkey.service
 create mode 100644 meta/recipes-devtools/distcc/files/distccd.service
 create mode 100644 meta/recipes-extended/at/files/atd.service

-- 
1.7.9.5



             reply	other threads:[~2014-01-20  2:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20  2:22 Chen Qi [this message]
2014-01-20  2:22 ` [PATCH V3 1/5] systemd: add 'less' to its RRECOMMENDS Chen Qi
2014-01-20  8:06   ` Bernhard Reutner-Fischer
2014-01-20  8:35     ` ChenQi
2014-01-22 10:00       ` Bernhard Reutner-Fischer
     [not found]         ` <52DF98A1.4090206@windriver.com>
     [not found]           ` <CAC1BbcRWE7cEpnfBA5JwVKgmXwSMWW85GjPPMVW9C5Y=HFZS5A@mail.gmail.com>
2014-01-23  8:23             ` ChenQi
     [not found]               ` <143c0d151a0.2760.0f39ed3bcad52ef2c88c90062b7714dc@gmail.com>
2014-01-23 20:41                 ` Bernhard Reutner-Fischer
2014-01-20  2:23 ` [PATCH V3 2/5] dropbear: add systemd unit files Chen Qi
2014-01-20  2:23 ` [PATCH V3 3/5] openssh: fixes for systemd Chen Qi
2014-01-20  2:23 ` [PATCH V3 4/5] distcc: add systemd support Chen Qi
2014-01-20  2:23 ` [PATCH V3 5/5] at: " Chen Qi

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.1390184362.git.Qi.Chen@windriver.com \
    --to=qi.chen@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 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.