From: Patrick McHardy <kaber@trash.net>
To: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Lost patches
Date: Fri, 12 May 2006 09:27:41 +0200 [thread overview]
Message-ID: <446438ED.3080304@trash.net> (raw)
I have the ungood feeling that I somehow managed to loose a couple
of patches I had originally queued for 2.6.17 but then delayed them
to 2.6.18. I couldn't find anything in the archives, but if anyone
has sent me patches that aren't already in mainline and are not in
the list below please resend or point me to the first submission.
Thanks.
Eric Leblond:
[NETFILTER]: conntrack: add fixed timeout flag in connection tracking
Patrick McHardy:
[NETFILTER]: Remove some useless casts
[NETFILTER]: {ip,nf}_conntrack_ftp: small optimization
[NETFILTER]: NAT: avoid unnecessary tuple inversions
[NETFILTER]: x_tables: add SCTP/DCCP support to
hashlimit/multiport/CLUSTERIP
[NETFILTER]: {ip,nf}_conntrack: make checksumming optional
[NETFILTER]: x_tables: add quota match
[NETFILTER]: ctnetlink: fix NAT configuration
[NETFILTER]: ctnetlink: fix conntrack mark change notifications
[NETFILTER]: x_tables: add statistic match
[NETFILTER]: ctnetlink: change table dumping not to require an
unique ID
reply other threads:[~2006-05-12 7:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=446438ED.3080304@trash.net \
--to=kaber@trash.net \
--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.