netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Mart Frauenlob <mart.frauenlob@chello.at>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] - libxt_bpf: use correct shell term in man page description
Date: Fri, 19 Apr 2013 02:16:50 +0200	[thread overview]
Message-ID: <20130419001650.GA24191@localhost> (raw)
In-Reply-To: <51627C59.6010407@chello.at>

On Mon, Apr 08, 2013 at 10:14:17AM +0200, Mart Frauenlob wrote:
> Hello,
> 
> use 'command substitution' as correct shell term instead of 'backticks'.
> Also mention backquotes and `$()' form.

I have applied this change to clarify this:

diff --git a/extensions/libxt_bpf.man b/extensions/libxt_bpf.man
index 4120a23..3dd4830 100644
--- a/extensions/libxt_bpf.man
+++ b/extensions/libxt_bpf.man
@@ -2,7 +2,7 @@ Match using Linux Socket Filter. Expects a BPF program
in decimal format. This
 is the format generated by the \fBnfbpf_compile\fP utility.
 .TP
 \fB\-\-bytecode\fP \fIcode\fP
-Pass the code in backtick format as argument.
+Pass the BPF bytes code format (described in the example below).
 .PP
 The code format is similar to the output of the tcpdump -ddd command: one line
 that stores the number of instructions, followed by one line for each

> btw: After compiling in the git directory the nfbpf_compile binary
> is shown as new file by git. Should that be so?

I have also fixed this.

Regards.

      reply	other threads:[~2013-04-19  0:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08  8:14 [PATCH] - libxt_bpf: use correct shell term in man page description Mart Frauenlob
2013-04-19  0:16 ` Pablo Neira Ayuso [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=20130419001650.GA24191@localhost \
    --to=pablo@netfilter.org \
    --cc=mart.frauenlob@chello.at \
    --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;
as well as URLs for NNTP newsgroup(s).