From: Xavier Stonestreet <firstname.lastname@example.org>
Subject: Re: s6-permafailon not acting as expected
Date: Wed, 18 Nov 2020 18:22:57 +0100 [thread overview]
Message-ID: <CAK-rGML2j+Jofkh9YQEskg4a99P0s87zYJbCqX4ejpDo46SRgA@mail.gmail.com> (raw)
In case you missed it, I'm reposting my question. If you're too busy
to respond, no worries, I'll understand. Thanks.
> I'm working on a bigger release (with some interface changes and a
> major version bump) that should happen before the end of the year, but
> not right now ^^'
Sounds good. So what kind of interface changes should we expect? I
mean will they require updating the service definitions, run/finish
scripts, that sort of thing?
next prev parent reply other threads:[~2020-11-18 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 18:01 Xavier Stonestreet
2020-11-16 22:05 ` Laurent Bercot
2020-11-17 15:32 ` Xavier Stonestreet
2020-11-17 18:43 ` Xavier Stonestreet
2020-11-17 20:06 ` Xavier Stonestreet
2020-11-17 21:42 ` Laurent Bercot
2020-11-18 17:22 ` Xavier Stonestreet [this message]
2020-11-18 18:35 ` Laurent Bercot
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).