From: Patrick McHardy <kaber@trash.net>
To: "Hervé Eychenne" <rv@wallfire.org>
Cc: Peter Warasin <peter@endian.com>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] iptables-restore: renames --test to --dry-run
Date: Thu, 08 Nov 2007 00:26:52 +0100 [thread overview]
Message-ID: <473249BC.2020406@trash.net> (raw)
In-Reply-To: <20071107230852.GA3206@eychenne.org>
Hervé Eychenne wrote:
> 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?
I'm not aware of such a thing, but what works pretty well for me is
to use stgit and selectively pull chunks to patches earlier in the
series and merge the top again.
So its something like:
- do lots of changes, commit on top of stack
- open in editor, pop patch
- create new patch, copy stuff from open editor
- commit
- go to top of stack again, merge
- repeat from step 2 until patch at top is empty
Its works quite fast since the merging goes really painlessly.
-
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:27 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
2007-11-07 23:26 ` Patrick McHardy [this message]
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=473249BC.2020406@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=peter@endian.com \
--cc=rv@wallfire.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.