From: Stephen Hemminger <stephen@networkplumber.org>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] man ip-link: Add missing lowpan link type
Date: Mon, 11 May 2015 09:21:46 -0700 [thread overview]
Message-ID: <20150511092146.148846e5@urahara> (raw)
In-Reply-To: <20150511071714.GP11014@wantstofly.org>
On Mon, 11 May 2015 10:17:14 +0300
Lennert Buytenhek <buytenh@wantstofly.org> wrote:
> Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
> ---
> These man pages don't use .nh when describing command invocation syntax,
> so we end up with things like this (on 80 character terminals):
>
> ip link add DEVICE type vxlan id ID [ dev PHYS_DEV ] [ { group
> | remote } IPADDR ] [ local IPADDR ] [ ttl TTL ] [ tos TOS ] [
> port MIN MAX ] [ [no]learning ] [ [no]proxy ] [ [no]rsc ] [
> [no]l2miss ] [ [no]l3miss ] [ ageing SECONDS ] [ maxaddress NUM‐
> BER ] [ gbp ]
>
> and:
>
> ip link add DEVICE type { gre | ipip | sit } remote ADDR local
> ADDR [ encap { fou | gue | none } ] [ encap-sport { PORT | auto
> } ] [ encap-dport PORT ] [ [no]encap-csum ] [ [no]encap-remc‐
> sum ]
>
> and this affects this addition as well:
>
> TYPE := [ bridge | bond | can | dummy | hsr | ifb | ipoib | macvlan |
> macvtap | vcan | veth | vlan | vxlan | ip6tnl | ipip | sit |
> gre | gretap | ip6gre | ip6gretap | vti | nlmon | ipvlan | low‐
> pan ]
>
> A possible fix for this would be to put these descriptions in an
> environment with hyphenation mode zero.
>
Applied.
Not sure what the best silly nroff fix for the hyphenation nonsense is.
prev parent reply other threads:[~2015-05-11 16:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 7:17 [PATCH iproute2] man ip-link: Add missing lowpan link type Lennert Buytenhek
2015-05-11 16:21 ` Stephen Hemminger [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=20150511092146.148846e5@urahara \
--to=stephen@networkplumber.org \
--cc=buytenh@wantstofly.org \
--cc=netdev@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