All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mart Frauenlob <mart.frauenlob@chello.at>
To: netfilter-devel@vger.kernel.org
Subject: [PATCH] - libxt_bpf: use correct shell term in man page description
Date: Mon, 08 Apr 2013 10:14:17 +0200	[thread overview]
Message-ID: <51627C59.6010407@chello.at> (raw)

[-- Attachment #1: Type: text/plain, Size: 258 bytes --]

Hello,

use 'command substitution' as correct shell term instead of 'backticks'.
Also mention backquotes and `$()' form.

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

Best regards

Mart

[-- Attachment #2: libxt_bpf.man-Use-correct-shell-term-in-man-page.patch --]
[-- Type: text/plain, Size: 964 bytes --]

>From 536c34c67b4149e7c83f474350d8a5fbaaa0fa6d Mon Sep 17 00:00:00 2001
From: Mart Frauenlob <mart.frauenlob@chello.at>
Date: Mon, 8 Apr 2013 10:03:22 +0200
Subject: [PATCH] libxt_bpf.man: Use correct shell term in man page.

---
 extensions/libxt_bpf.man |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/extensions/libxt_bpf.man b/extensions/libxt_bpf.man
index 4120a23..675effd 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 code as argument using command substitution (backquotes or `$()' form).
 .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
-- 
1.7.2.5


             reply	other threads:[~2013-04-08  8:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08  8:14 Mart Frauenlob [this message]
2013-04-19  0:16 ` [PATCH] - libxt_bpf: use correct shell term in man page description Pablo Neira Ayuso

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=51627C59.6010407@chello.at \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.