From: Florian Westphal <fw@strlen.de>
To: Johannes Truschnigg <johannes@truschnigg.info>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: ebtables-save: Do string processing in perl instead of shell
Date: Tue, 30 Sep 2025 12:21:38 +0200 [thread overview]
Message-ID: <aNuvKZN9WM8bVRkn@strlen.de> (raw)
In-Reply-To: <20250927131421.24756-2-johannes@truschnigg.info>
Johannes Truschnigg <johannes@truschnigg.info> wrote:
> want to consider merging this small improvement.
Would you mind resending this with a Signed-off-by tag?
(git commit --amend -s)
Thanks.
next prev parent reply other threads:[~2025-09-30 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-27 13:00 ebtables-save: Do string processing in perl instead of shell Johannes Truschnigg
2025-09-27 13:00 ` [PATCH] Don't shell out for getting current date and table names Johannes Truschnigg
2025-09-30 10:21 ` Florian Westphal [this message]
2025-09-30 18:06 ` Re: ebtables-save: Do string processing in perl instead of shell Johannes Truschnigg
2025-09-30 18:06 ` [PATCH v2] Don't shell out for getting current date and table names Johannes Truschnigg
2025-09-30 19:13 ` Florian Westphal
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=aNuvKZN9WM8bVRkn@strlen.de \
--to=fw@strlen.de \
--cc=johannes@truschnigg.info \
--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 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).