From: Arturo Borrero Gonzalez <arturo@debian.org>
To: Jan Engelhardt <ej@inai.de>, Duncan Roe <duncan_roe@optusnet.com.au>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Jan Engelhardt <jengelh@inai.de>,
netfilter-devel@vger.kernel.org, fw@strlen.de,
matthias.gerstner@suse.com, phil@nwl.cc, eric@garver.life
Subject: Re: [PATCH] tools: add a systemd unit for static rulesets
Date: Sun, 23 Mar 2025 11:00:40 +0100 [thread overview]
Message-ID: <5bf4cd03-ddb3-4cc4-b07e-e25e475395f8@debian.org> (raw)
In-Reply-To: <22n4s4s4-8155-708o-4091-q6o3nq313641@vanv.qr>
On 3/22/25 10:24, Jan Engelhardt wrote:
>
> On Saturday 2025-03-22 02:49, Duncan Roe wrote:
>>>
>>> I have mixed feelings about having this systemd service file in this repository.
>>> Will this file be maintained wrt. systemd ecosystem updates? Or will it be
>>> outdated and neglected after a few years?
>
> There are no changes expected to be necessary.
>
How so?
Is the systemd ecosystem not evolving? Won't systemd see any updates? Will it
not deprecate options, or introduce new ones, thus making the systemd service
file outdated?
I don't think 'no changes expected to be necessary' is a statement that can be
applied to any software system.
next prev parent reply other threads:[~2025-03-23 10:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 20:59 [PATCH] tools: add a systemd unit for static rulesets Jan Engelhardt
2025-03-05 21:35 ` Pablo Neira Ayuso
2025-03-21 13:29 ` Arturo Borrero Gonzalez
2025-03-22 1:49 ` Duncan Roe
2025-03-22 9:24 ` Jan Engelhardt
2025-03-23 10:00 ` Arturo Borrero Gonzalez [this message]
2025-03-23 13:34 ` Jan Engelhardt
2025-03-23 21:04 ` Phil Sutter
2025-03-23 10:24 ` Pablo Neira Ayuso
2025-03-06 14:16 ` Eric Garver
2025-03-20 14:05 ` Phil Sutter
2025-03-22 9:46 ` Jan Engelhardt
2025-03-25 1:34 ` Dan Winship
2025-03-26 15:56 ` Phil Sutter
2025-03-26 22:21 ` Jan Engelhardt
2025-04-17 12:39 ` Pablo Neira Ayuso
2025-03-27 11:12 ` Dan Winship
2025-03-27 13:29 ` Phil Sutter
2025-03-22 9:41 ` Jan Engelhardt
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=5bf4cd03-ddb3-4cc4-b07e-e25e475395f8@debian.org \
--to=arturo@debian.org \
--cc=duncan_roe@optusnet.com.au \
--cc=ej@inai.de \
--cc=eric@garver.life \
--cc=fw@strlen.de \
--cc=jengelh@inai.de \
--cc=matthias.gerstner@suse.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
/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).