From: Alyssa Ross <hi@alyssa.is>
To: Demi Marie Obenour <demiobenour@gmail.com>
Cc: Spectrum OS Development <devel@spectrum-os.org>
Subject: Re: [PATCH v6 1/2] tools: Add adapter tool for services using sd_notify
Date: Thu, 06 Nov 2025 10:41:08 +0100 [thread overview]
Message-ID: <87zf8zxzuz.fsf@alyssa.is> (raw)
In-Reply-To: <cea8e90d-7457-4d07-9e81-399e92b2f342@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 624 bytes --]
Demi Marie Obenour <demiobenour@gmail.com> writes:
> On 11/3/25 03:29, Demi Marie Obenour wrote:
>> This adapts programs using sd_notify for use with s6 readiness
>> notification. stdin and stdout are hard-coded for simplicity.
>>
>> Signed-off-by: Demi Marie Obenour <demiobenour@gmail.com>
>
> Sorry for the repeated posts. I screwed up b4's internal state and
> my attempt to repair it just made things worse.
>
> Is there a way to get b4 to go back and use a different post as the
> previous one, so I can fix threading in situations like this one?
Not sure. I haven't used b4 for patch submission.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2025-11-06 9:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 8:29 [PATCH v6 0/2] Switch from mdevd to systemd-udevd in root filesystem Demi Marie Obenour
2025-11-03 8:29 ` [PATCH v6 1/2] tools: Add adapter tool for services using sd_notify Demi Marie Obenour
2025-11-03 8:33 ` Demi Marie Obenour
2025-11-06 9:41 ` Alyssa Ross [this message]
2025-11-06 9:49 ` Alyssa Ross
2025-11-03 8:29 ` [PATCH v6 2/2] host/rootfs: Switch to systemd-udevd Demi Marie Obenour
2025-11-06 9:55 ` Alyssa Ross
-- strict thread matches above, loose matches on Subject: below --
2025-11-07 19:00 [PATCH v6 0/2] Switch from mdevd to systemd-udevd in root filesystem Demi Marie Obenour
2025-11-07 19:00 ` [PATCH v6 1/2] tools: Add adapter tool for services using sd_notify Demi Marie Obenour
2025-11-09 13:58 ` Alyssa Ross
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=87zf8zxzuz.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=demiobenour@gmail.com \
--cc=devel@spectrum-os.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.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
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).