From: "Hervé Eychenne" <rv@wallfire.org>
To: Peter Warasin <peter@endian.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] iptables-restore: renames --test to --dry-run
Date: Thu, 8 Nov 2007 00:08:52 +0100 [thread overview]
Message-ID: <20071107230852.GA3206@eychenne.org> (raw)
In-Reply-To: <47322D4A.3090201@endian.com>
On Wed, Nov 07, 2007 at 10:25:30PM +0100, Peter Warasin wrote:
Hi,
> The following patch renames the option --test (-t) to --dry-run (-d)
> in order to free the letter 't' for --table, which makes the options
> more consistent regarding the other *tables tools, where -t is always
> --table.
Well, a long time ago (more than 3 years, a few days before the 2004
workshop), I had sent a big patch which contained among others things:
- the ability to restore only one table
- a better(?) testing mode
This patch was juged too big (72 KB) and it was not applied:
I admit I should have broken it up into many smaller patches, but the
amount of work was somewhat discouraging.
Well, I'm glad some of these ideas have been resurfacing in (smaller)
pieces over time.
Here are some thoughts (dating from this time) related to testing
mode:
- the -d option is generally used (as a debug switch). The one-letter
equivalent of --dry-run is generally -n.
- I had taken a different approach than the existing one for "testing
mode". I think I can recall having encountered some problems
with the current approach, but I cannot remember which ones exactly
after all this time.
Anyway, I ended up implementing testing mode at the libiptc level,
which is better as it is more generic and enables to validate iptables
command line (and not only iptables-restore file) syntax as well.
I wish I had the courage and the time to go through my old big patch
and extract the things that are still relevant today.
I had asked at that time to this list if someone knew a patch splitter
GUI, that would enable to split a patch into several (sub)patches by
graphically selecting which changes would go to each (sub)patch.
Maybe there has been some progress on this, or some new well-informed
readers?
Herve
--
_
(°= Hervé Eychenne
//) Homepage: http://www.eychenne.org/
v_/_ WallFire project: http://www.wallfire.org/
-
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-11-07 23:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 21:25 [PATCH] iptables-restore: renames --test to --dry-run Peter Warasin
2007-11-07 23:08 ` Hervé Eychenne [this message]
2007-11-07 23:26 ` Patrick McHardy
2007-11-08 9:02 ` Jan Engelhardt
2007-11-08 9:16 ` Herve Eychenne
2007-11-08 10:07 ` Peter Warasin
2007-11-08 10:26 ` Herve Eychenne
2007-11-08 9:44 ` Amin Azez
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=20071107230852.GA3206@eychenne.org \
--to=rv@wallfire.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=peter@endian.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 NNTP newsgroup(s).