From: Alexis <flexibeast@gmail.com>
To: supervision@list.skarnet.org
Subject: Re: [svlogd] / -ttt / why UTC?
Date: Fri, 07 Apr 2023 09:21:44 +1000 [thread overview]
Message-ID: <87o7o061b8.fsf@ada> (raw)
In-Reply-To: <em6d775667-2984-4189-ae5a-33038b86fe75@f9605eea.com>
"Laurent Bercot" <ska-supervision@skarnet.org> writes:
> The way to go about it would be to implement the functionality
> yourself, and submit a patch; that said, since the last time we
> saw
> svlogd's maintainer was four years ago in a flash
Well, Void maintains its own runit repo:
https://github.com/void-linux/runit
So one could open an issue there and ask if a PR implementing this
functionality would be considered.
Alexis.
prev parent reply other threads:[~2023-04-06 23:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1799590563.259018.1680775861585.ref@mail.yahoo.com>
2023-04-06 10:11 ` cpt.arsemerica.yahoo.com via supervision
2023-04-06 11:02 ` Laurent Bercot
2023-04-06 12:47 ` cpt.arsemerica.yahoo.com via supervision
2023-04-06 18:12 ` Laurent Bercot
2023-04-06 20:37 ` cpt.arsemerica.yahoo.com via supervision
2023-04-09 6:11 ` Jonathan de Boyne Pollard
2023-04-06 23:21 ` Alexis [this message]
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=87o7o061b8.fsf@ada \
--to=flexibeast@gmail.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).