From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: Re: fwd: Move libipt_recent to libxt_recent
Date: Tue, 14 Oct 2008 13:59:36 +0200 [thread overview]
Message-ID: <48F489A8.5090002@trash.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0810131443300.20759@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> Move libipt_recent to libxt_recent
This patch does not apply:
patching file extensions/libipt_recent.c
Hunk #1 FAILED at 5.
Hunk #2 FAILED at 46.
Hunk #3 succeeded at 74 (offset -5 lines).
Hunk #4 succeeded at 96 (offset -5 lines).
Hunk #5 succeeded at 107 (offset -5 lines).
Hunk #6 succeeded at 121 (offset -5 lines).
Hunk #7 FAILED at 152.
Hunk #8 FAILED at 163.
Hunk #9 succeeded at 216 (offset -9 lines).
4 out of 9 hunks FAILED -- saving rejects to file
extensions/libipt_recent.c.rej
patching file extensions/libipt_recent.man
patching file include/linux/netfilter/xt_recent.h
patching file include/linux/netfilter_ipv4/ipt_recent.h
next prev parent reply other threads:[~2008-10-14 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 18:43 fwd: Move libipt_recent to libxt_recent Jan Engelhardt
2008-10-14 11:59 ` Patrick McHardy [this message]
2008-10-22 6:56 ` 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=48F489A8.5090002@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@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