From: "David S. Miller" <davem@redhat.com>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH 2.6 0/12]: netfilter update
Date: Tue, 21 Sep 2004 14:36:11 -0700 [thread overview]
Message-ID: <20040921143611.6a6e2f60.davem@redhat.com> (raw)
In-Reply-To: <414F9DFC.701@trash.net>
On Tue, 21 Sep 2004 05:20:28 +0200
Patrick McHardy <kaber@trash.net> wrote:
> following are 12 mostly random netfilter patches for 2.6.
> You can also pull all changes from bk://212.42.230.204/2.6-netfilter
There are big conflicts with Rusty's recent
seq file fixes to ip_conntrack_standalone.c
Please resync with Linus's current tree and
use "bk resolve" or whatever means to fix this
up.
next prev parent reply other threads:[~2004-09-21 21:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 3:20 [PATCH 2.6 0/12]: netfilter update Patrick McHardy
2004-09-21 21:36 ` David S. Miller [this message]
2004-09-21 23:38 ` Patrick McHardy
2004-09-22 0:18 ` David S. Miller
2004-09-22 1:42 ` Patrick McHardy
2004-09-24 22:40 ` David S. Miller
2004-09-26 19:43 ` Patrick McHardy
2004-09-26 21:45 ` Henrik Nordstrom
2004-09-26 21:56 ` Patrick McHardy
2004-09-26 22:08 ` Henrik Nordstrom
2004-09-26 23:19 ` Patrick McHardy
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=20040921143611.6a6e2f60.davem@redhat.com \
--to=davem@redhat.com \
--cc=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.