From: multiplexd <multiplexd@gmx.com>
To: Supervision <supervision@list.skarnet.org>
Subject: Re: s6-ps
Date: Sat, 5 Jan 2019 15:29:10 +0000 [thread overview]
Message-ID: <20190105152910.x2a7gxyi3a2jr3br@flywheel> (raw)
In-Reply-To: <f54a9d22-567a-f238-eae3-915280745c26@NTLWorld.COM>
Hi all,
(Apologies to JdePB, I accidentally replied to him directly instead of
to the supervision list.)
On Sat, Jan 05, 2019 at 10:46:29AM +0000, Jonathan de Boyne Pollard wrote:
> Alas, the Debian world has not yet caught up with the other
> toolsets, and the third-party Debian packaging for s6-linux-utils and the
> others has yet to make it into Debian's own repository.
>
> * https://github.com/multiplexd/s6-packaging
>
Thanks for the advertising, Jonathan :-). I would, however, like to note
that getting that packaging into the official Debian repos is not an
immediate goal for me, as I don't have the time to commit to being a
Debian package maintainer for the forseeable future.
Cheers,
--multiplexd.
next prev parent reply other threads:[~2019-01-05 15:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9f647c4c-2dc3-b977-928c-ee164ba88afe@ntlworld.com>
2019-01-05 0:20 ` s6-ps Laurent Bercot
2019-01-05 4:04 ` s6-ps Jonathan de Boyne Pollard
2019-01-05 10:46 ` s6-ps Jonathan de Boyne Pollard
2019-01-05 14:41 ` s6-ps Jonathan de Boyne Pollard
2019-01-05 15:29 ` multiplexd [this message]
2019-01-05 20:30 ` Can s6 be enough?: was s6-ps Steve Litt
2019-01-05 21:22 ` Laurent Bercot
[not found] ` <20190106053901.GA16647@latitude.localdomain>
2019-01-06 7:40 ` Laurent Bercot
2019-01-06 15:03 ` Brett Neumeier
2019-01-07 21:45 ` Steve Litt
2019-01-08 9:19 ` Laurent Bercot
2019-01-05 21:00 ` s6-ps Guillermo
2019-01-06 1:15 ` s6-ps Steve Litt
2019-01-06 7:06 ` s6-ps Colin Booth
2019-01-06 7:30 ` s6-ps Laurent Bercot
2019-01-06 18:07 ` s6-ps Colin Booth
2019-01-04 9:18 s6-ps Jonathan de Boyne Pollard
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=20190105152910.x2a7gxyi3a2jr3br@flywheel \
--to=multiplexd@gmx.com \
--cc=supervision@list.skarnet.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;
as well as URLs for NNTP newsgroup(s).