From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: pablo@netfilter.org,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: doc: escape minus sign in manpages
Date: Mon, 12 Jan 2009 07:20:56 +0100 [thread overview]
Message-ID: <496AE148.6000909@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.00.0901120706460.21692@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> Hm I noticed I still had something in my index that
> puts back hyphens where they belong. Here goes:
>
>
> parent fea74bf74ff524431ce65145f1523584edf99dc9 (v1.4.3-rc1-16-gfea74bf)
> commit de2a83cb5022c429ccf1b852688481a0d8ad95e5
> Author: Jan Engelhardt <jengelh@medozas.de>
> Date: Mon Jan 12 07:06:12 2009 +0100
>
> doc: escape minus sign in manpage (2)
Something in this patch seems to be confusing "patch":
patching file ip6tables.8.in
patching file iptables.8.in
Hunk #1 FAILED at 23.
1 out of 1 hunk FAILED -- saving rejects to file iptables.8.in.rej
missing header for unified diff at line 388 of patch
can't find file to patch at input line 388
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
| tables of IPv4 packet
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
9 out of 9 hunks ignored
next prev parent reply other threads:[~2009-01-12 6:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 2:13 doc: escape minus sign in manpages Jan Engelhardt
2009-01-09 20:54 ` ENOBUF error during recv Ryan VanRiper
2009-01-09 22:09 ` Eric Leblond
2009-01-12 1:36 ` doc: escape minus sign in manpages Pablo Neira Ayuso
2009-01-12 2:39 ` Jan Engelhardt
2009-01-12 3:53 ` Patrick McHardy
2009-01-12 6:07 ` Jan Engelhardt
2009-01-12 6:20 ` Patrick McHardy [this message]
2009-01-14 5:47 ` Jan Engelhardt
2009-01-16 8:05 ` Patrick McHardy
2009-01-16 8:19 ` Jan Engelhardt
2009-01-19 14:35 ` 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=496AE148.6000909@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).