From: Steven Van Acker <deepstar+NRpGDEuW@singularity.be>
To: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Cc: Patrick McHardy <kaber@trash.net>,
Mickael Marchand <marchand@kde.org>,
kulnet@kulnet.kuleuven.be
Subject: Re: rtsp-conntrack without needing NAT
Date: Fri, 15 Sep 2006 10:40:43 +0200 [thread overview]
Message-ID: <20060915084043.GA15799@ekonomika.be> (raw)
In-Reply-To: <20060915081547.GA26883@ekonomika.be>
On Fri, Sep 15, 2006 at 10:15:47AM +0200, Steven Van Acker wrote:
> Sorry about that. I recreated the patch based on
> the latest pom-ng snapshot (patch-o-matic-ng-20060914)
Umph, this is getting really embarassing...
Someone complained that I didn't use the --ignore-space-change and
--ignore-tab-expansion options of diff, resulting in a large patchfile.
I recreated the patchfile again.
kinds regards,
-- Steven
next prev parent reply other threads:[~2006-09-15 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 12:51 rtsp-conntrack without needing NAT Steven Van Acker
2006-09-15 4:40 ` Patrick McHardy
2006-09-15 8:15 ` Steven Van Acker
2006-09-15 8:40 ` Steven Van Acker [this message]
2006-09-15 8:43 ` Steven Van Acker
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=20060915084043.GA15799@ekonomika.be \
--to=deepstar+nrpgdeuw@singularity.be \
--cc=kaber@trash.net \
--cc=kulnet@kulnet.kuleuven.be \
--cc=marchand@kde.org \
--cc=netfilter-devel@lists.netfilter.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.