Linux Netfilter development
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Max Kellermann <max@duempel.org>,
	Netfilter Developer Mailing List
	<netfilter-devel@vger.kernel.org>
Subject: Re: manpages: consistent syntax
Date: Thu, 05 Jun 2008 16:51:36 +0200	[thread overview]
Message-ID: <4847FD78.5020906@trash.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0806051647590.29055@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> On Monday 2008-06-02 12:49, Patrick McHardy wrote:
>> Jan Engelhardt wrote:
>>> commit 314cc5f0dd48c047e660f45aaaf4e86675ab5d74
>>> Author: Jan Engelhardt <jengelh@medozas.de>
>>> Date:   Tue May 6 19:47:33 2008 +0200
>>>
>>>     manpages: consistent syntax
>>>     
>>>     In the manpages, bold is used to denote characters the user has to
>>>     enter verbatim, italic denotes placeholders and non-highlighted
>>>     pieces are used as a structure: "[]" specifying an optional part,
>>>     "{}" a mandatory part, with "|" used for alternations. The "!" for
>>>     negation is better supported before the option than after it, too.
>>>     The patch makes a few files consistent with this style already used
>>>     in manpages.
>> Applied, thanks. Please remember to sign off iptables patches in the
>> future.
> 
> I guess that's why it says Author: Patrick McHardy for this one in git.. :-)

Probably. I usually use a correct authorname anyway, but seems
I forgot this time.


      reply	other threads:[~2008-06-05 14:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-28 15:04 [PATCH] fixed the position of the exclamation mark Max Kellermann
2008-05-28 16:42 ` Jan Engelhardt
2008-05-28 16:45   ` manpages: consistent syntax Jan Engelhardt
2008-06-02 10:49     ` Patrick McHardy
2008-06-05 14:48       ` Jan Engelhardt
2008-06-05 14:51         ` Patrick McHardy [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=4847FD78.5020906@trash.net \
    --to=kaber@trash.net \
    --cc=jengelh@medozas.de \
    --cc=max@duempel.org \
    --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