From: Stephen Hemminger <shemminger@osdl.org>
To: bridge@lists.osdl.org
Subject: Re: [Bridge] bridge nf vs. 2.4.29
Date: Wed, 2 Feb 2005 00:10:21 -0800 [thread overview]
Message-ID: <20050202001021.52465d7a@localhost.localdomain> (raw)
In-Reply-To: <41FF84EB.3000802@gmx.net>
On Tue, 01 Feb 2005 14:32:27 +0100
Marc Müller <marc.muller@gmx.net> wrote:
> Hello List,
>
> Are there any known issues in using the bridge-nf patch for kernel
> v2.4.28 against 2.4.29 or can it be used in production environments?
If it applies clean you should be okay.
is
> there already an adopted version of the patch for 2.4.29?
> Sorry if this question has already been answered elsewhere (I didn't
> find something useful on google, cvs and the list).
Check ebtables-users@lists.sourceforge.net
prev parent reply other threads:[~2005-02-02 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 13:32 [Bridge] bridge nf vs. 2.4.29 Marc Müller
2005-02-02 8:10 ` Stephen Hemminger [this message]
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=20050202001021.52465d7a@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=bridge@lists.osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox