All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>
Cc: netfilter-devel@vger.kernel.org, jengelh@inai.de
Subject: Re: [PATCH 0/8] improve systemd service
Date: Wed, 29 Oct 2025 12:40:57 +0100	[thread overview]
Message-ID: <aQH9SaAdc8fDKjcc@strlen.de> (raw)
In-Reply-To: <b66cb7d6e998dcb76cee90694d4632c6d7122153.camel@christoph.anton.mitterer.name>

Christoph Anton Mitterer <mail@christoph.anton.mitterer.name> wrote:
> On Tue, 2025-10-28 at 17:33 +0100, Florian Westphal wrote:
> > > This is a first series of patches that tries to improve the
> > > included
> > > `nftables.service`.
> > 
> > Sir, this is netfilter-devel and not nftables-systemd-devel@.
> 
> Uhm? nftables ships the .service file, none of this was about systemd
> development itself, there doesn't seem to be a dedicated list for
> nftables and no one complained about me posting nftables manpage
> patches on netfilter-devel.

I don't have the expertise to review systemd service files.

> > I see Jans original service file) as convinience / ease-of-use
> > contribution
> > not as something that should be maintained continuously.
> 
> Hope that I don't negatively affect anyone's use case for this, but if
> the file isn't meant to be maintained, shouldn't it then rather be
> dropped?

If this thing needs constant changes then yes, absolutely.

  reply	other threads:[~2025-10-29 11:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-24  2:08 [PATCH 0/8] improve systemd service Christoph Anton Mitterer
2025-10-24  2:08 ` [PATCH 1/9] tools: don’t set options whose values match their defaults Christoph Anton Mitterer
2025-10-24  2:08 ` [PATCH 2/9] tools: use the same pair of boolean literals Christoph Anton Mitterer
2025-10-24  2:08 ` [PATCH 3/9] tools: include further `Documentation=` URIs Christoph Anton Mitterer
2025-10-24  2:08 ` [PATCH 4/9] tools: reorder options Christoph Anton Mitterer
2025-10-28 17:15   ` Jan Engelhardt
2025-10-29  0:29     ` Christoph Anton Mitterer
2025-10-24  2:08 ` [PATCH 5/9] tools: depend on `sysinit.target` Christoph Anton Mitterer
2025-10-28 17:19   ` Jan Engelhardt
2025-10-29  0:35     ` Christoph Anton Mitterer
2025-10-24  2:08 ` [PATCH 6/9] tools: don’t stop `nftables.service` (and flush the ruleset) on shutdown Christoph Anton Mitterer
2025-10-24  2:08 ` [PATCH 7/9] tools: don’t stop `nftables.service` (and flush the ruleset) when isolating another unit Christoph Anton Mitterer
2025-10-24  2:08 ` [PATCH 8/9] tools: flush the ruleset only on an actual dedicated unit stop Christoph Anton Mitterer
2025-10-28 17:31   ` Jan Engelhardt
2025-10-28 17:37     ` Florian Westphal
2025-10-29  0:41     ` Christoph Anton Mitterer
2025-10-29 10:07       ` Jan Engelhardt
2025-10-30  0:53         ` Christoph Anton Mitterer
2025-10-30 23:34   ` Christoph Anton Mitterer
2025-10-24  2:08 ` [PATCH 9/9] tools: let the unit fail if the rules file is missing Christoph Anton Mitterer
2025-10-28 16:33 ` [PATCH 0/8] improve systemd service Florian Westphal
2025-10-29  0:27   ` Christoph Anton Mitterer
2025-10-29 11:40     ` Florian Westphal [this message]
2025-10-29 12:07       ` 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=aQH9SaAdc8fDKjcc@strlen.de \
    --to=fw@strlen.de \
    --cc=jengelh@inai.de \
    --cc=mail@christoph.anton.mitterer.name \
    --cc=netfilter-devel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.