From: joeja@mindspring.com
To: jjs@pobox.com
Cc: jgarzik@mandrakesoft.com, linux-kernel@vger.kernel.org
Subject: Re: Re: loop back broken in 2.2.14
Date: Mon, 12 Nov 2001 12:40:43 -0500 [thread overview]
Message-ID: <Springmail.105.1005586843.0.91657700@www.springmail.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
Okay, I can delete out those two lines to get loop working.
Is 2.4.x really a stable tree? Or should I wait for 2.4.25 before I consider it really stable?
> > François Cami wrote:
> >
> > > yes, see 2.4.15pre1
> > > warning, the iptables code in 2.4.15pre1 and pre2 seems broken.
> >
> > and further it is likely that pre3 fixes iptables code :)
> > (it looks like the patch got reverted)
>
> Actually it doesn't seem to be reverted,
> just reworked -
hmm, spoke too soon -
looks like they were reverted after all...
cu
jjs
next reply other threads:[~2001-11-12 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 17:40 joeja [this message]
2001-11-12 20:41 ` loop back broken in 2.2.14 J Sloan
-- strict thread matches above, loose matches on Subject: below --
2001-11-12 20:27 joeja
2001-11-14 6:31 ` Michael Peddemors
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=Springmail.105.1005586843.0.91657700@www.springmail.com \
--to=joeja@mindspring.com \
--cc=jgarzik@mandrakesoft.com \
--cc=jjs@pobox.com \
--cc=linux-kernel@vger.kernel.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