From: "William Hubbs" <williamh@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/openrc:0.34.x commit in: /
Date: Wed, 25 Oct 2017 20:25:16 +0000 (UTC) [thread overview]
Message-ID: <1508962553.3a96ca1c966c3cc44a2e0e51b383ab47d078bcc1.williamh@OpenRC> (raw)
commit: 3a96ca1c966c3cc44a2e0e51b383ab47d078bcc1
Author: William Hubbs <w.d.hubbs <AT> gmail <DOT> com>
AuthorDate: Wed Oct 25 20:15:53 2017 +0000
Commit: William Hubbs <williamh <AT> gentoo <DOT> org>
CommitDate: Wed Oct 25 20:15:53 2017 +0000
URL: https://gitweb.gentoo.org/proj/openrc.git/commit/?id=3a96ca1c
Update ChangeLog
ChangeLog | 39 ++++++++++++++++++++++++---------------
1 file changed, 24 insertions(+), 15 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index ea893f4d..0cbe56be 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,27 @@
+commit 934530914bd507476b428d3f6572bbb1c5bbfd16
+Author: William Hubbs <w.d.hubbs@gmail.com>
+Commit: William Hubbs <w.d.hubbs@gmail.com>
+
+ add "unsupervised" status and return code 64 to supervise-daemon status function
+
+ This is to be used if the service is being supervised and the
+ supervisor is somehow killed.
+
+ Currently, this is very linux specific, but I will expand to other
+ platforms, patches are welcome.
+
+commit b717625cd27950c3f00b5345bc1cee9700e79498
+Author: William Hubbs <w.d.hubbs@gmail.com>
+Commit: William Hubbs <w.d.hubbs@gmail.com>
+
+ version 0.34.2
+
+commit b47539613431521e5e99bc388e6a9d8eb0e48801
+Author: William Hubbs <w.d.hubbs@gmail.com>
+Commit: William Hubbs <w.d.hubbs@gmail.com>
+
+ Update ChangeLog
+
commit e7b1d898ca7896d6443ba1e5167eb6bcf3f92929
Author: William Hubbs <w.d.hubbs@gmail.com>
Commit: William Hubbs <w.d.hubbs@gmail.com>
@@ -1469,18 +1493,3 @@ Author: William Hubbs <w.d.hubbs@gmail.com>
Commit: William Hubbs <w.d.hubbs@gmail.com>
src/rc/rc: do not try to start services if fork fails
-
-commit 003657c973ea338a19f2b7294190af9d76cf5cea
-Author: Robin H. Johnson <robbat2@gentoo.org>
-Commit: William Hubbs <w.d.hubbs@gmail.com>
-
- init.d/loopback: drop scope on loopback
-
- Busybox does not support the 'scope' argument on 'ip address add' or 'ip
- route add', this is documented in BUSYBOX.md, but is no longer actually
- needed, as the kernel does get it right without manual specification,
- and the ifconfig variant already relies on the kernel to get it right.
- This is part of #103.
-
- X-Gentoo-Bug: 487208
- X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=487208
next reply other threads:[~2017-10-25 20:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 20:25 William Hubbs [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-26 19:01 [gentoo-commits] proj/openrc:0.34.x commit in: / William Hubbs
2017-10-26 19:04 William Hubbs
2017-10-26 19:19 William Hubbs
2017-10-28 0:29 William Hubbs
2017-10-28 0:29 William Hubbs
2017-11-07 21:39 William Hubbs
2017-11-07 21:39 William Hubbs
2017-11-07 21:39 William Hubbs
2017-11-07 22:09 William Hubbs
2017-11-13 23:37 William Hubbs
2017-11-13 23:56 William Hubbs
2017-11-16 22:39 William Hubbs
2017-11-16 22:39 William Hubbs
2017-11-20 17:52 William Hubbs
2017-11-20 18:42 William Hubbs
2017-11-27 19:09 William Hubbs
2017-11-27 19:09 William Hubbs
2017-11-29 22:10 William Hubbs
2017-11-29 22:10 William Hubbs
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=1508962553.3a96ca1c966c3cc44a2e0e51b383ab47d078bcc1.williamh@OpenRC \
--to=williamh@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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