From: Remco van 't Veer <remco@remworks.net>
To: Richard Sent <richard@freakingpenguin.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: add shepherd requirement to an existing service?
Date: Fri, 15 Mar 2024 10:22:47 +0100 [thread overview]
Message-ID: <87y1ajn920.fsf@remworks.net> (raw)
In-Reply-To: <87ttl8wvf5.fsf@freakingpenguin.com>
That's exactly what I need! Thanks!
prev parent reply other threads:[~2024-03-15 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 11:04 add shepherd requirement to an existing service? Remco van 't Veer
2024-03-11 18:59 ` Oleg Pykhalov
2024-03-12 10:25 ` Remco van 't Veer
2024-03-14 17:54 ` Richard Sent
2024-03-15 9:22 ` Remco van 't Veer [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1ajn920.fsf@remworks.net \
--to=remco@remworks.net \
--cc=help-guix@gnu.org \
--cc=richard@freakingpenguin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).