From: "David S. Miller" <davem@davemloft.net>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH 2.4 0/18]: Netfilter resync with 2.6
Date: Mon, 20 Dec 2004 16:55:09 -0800 [thread overview]
Message-ID: <20041220165509.152c058a.davem@davemloft.net> (raw)
In-Reply-To: <41C67BBB.6010100@trash.net>
On Mon, 20 Dec 2004 08:14:03 +0100
Patrick McHardy <kaber@trash.net> wrote:
> the following 18 patches resync netfilter in 2.4 with 2.6.
> They contains the ICMP+NAT fixes, Yasuyuki's IPv6 fixes
> and two misc. fixes.
>
> You can pull all changes from bk://212.42.230.204/nf-2.4
Please don't put things like the Bitkeeper/etc/config changeset
in your tree. I can't pull in changes like that.
Unfortunately, I can't even "bk undo -r" that bogus change since
it's not at the tip of the tree. And I don't want to "bk cset -x"
the changeset since that leaves the history of this crap in there.
Can you put together a clean tree without the Bitkeeper/etc/config
change in it? Thanks.
next prev parent reply other threads:[~2004-12-21 0:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 7:14 [PATCH 2.4 0/18]: Netfilter resync with 2.6 Patrick McHardy
2004-12-21 0:55 ` David S. Miller [this message]
2004-12-21 9:41 ` Patrick McHardy
2004-12-21 8:36 ` David S. Miller
2004-12-22 8:37 ` Patrick McHardy
2004-12-28 5:33 ` David S. Miller
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=20041220165509.152c058a.davem@davemloft.net \
--to=davem@davemloft.net \
--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.