From: Stephen Hemminger <stephen@networkplumber.org>
To: Phil Sutter <phil@nwl.cc>
Cc: Stephen Hemminger <shemming@brocade.com>, netdev@vger.kernel.org
Subject: Re: [iproute PATCH 0/6] iplink: Improve documentation
Date: Wed, 20 Jul 2016 12:13:07 -0700 [thread overview]
Message-ID: <20160720121307.20b6cbc6@xeon-e3> (raw)
In-Reply-To: <1468056170-6056-1-git-send-email-phil@nwl.cc>
On Sat, 9 Jul 2016 11:22:44 +0200
Phil Sutter <phil@nwl.cc> wrote:
> This series improves documentation around the feature of 'ip link set'
> to configure device type specific parameters. While doing so, I reviewed
> used fonts in ip-link.8 and fixed a few bugs/inconsistencies.
>
> Phil Sutter (6):
> iplink: List valid 'type' argument in ip link help text
> iplink: bond_slave: Add missing help functions
> ip-link.8: Extend type list in synopsis
> ip-link.8: Place 'ip link set' warning more prominently
> ip-link.8: Add slave type option descriptions
> ip-link.8: Fix font choices
>
> ip/iplink.c | 4 +-
> ip/iplink_bond_slave.c | 24 ++++
> man/man8/ip-link.8.in | 314 +++++++++++++++++++++++++++++++++++--------------
> 3 files changed, 254 insertions(+), 88 deletions(-)
>
Applied thanks
prev parent reply other threads:[~2016-07-20 19:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-09 9:22 [iproute PATCH 0/6] iplink: Improve documentation Phil Sutter
2016-07-09 9:22 ` [iproute PATCH 1/6] iplink: List valid 'type' argument in ip link help text Phil Sutter
2016-07-09 9:22 ` [iproute PATCH 2/6] iplink: bond_slave: Add missing help functions Phil Sutter
2016-07-09 9:22 ` [iproute PATCH 3/6] ip-link.8: Extend type list in synopsis Phil Sutter
2016-07-09 9:22 ` [iproute PATCH 4/6] ip-link.8: Place 'ip link set' warning more prominently Phil Sutter
2016-07-09 9:22 ` [iproute PATCH 5/6] ip-link.8: Add slave type option descriptions Phil Sutter
2016-07-09 9:22 ` [iproute PATCH 6/6] ip-link.8: Fix font choices Phil Sutter
2016-07-20 19:13 ` 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=20160720121307.20b6cbc6@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=phil@nwl.cc \
--cc=shemming@brocade.com \
/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).