From: Stephen Hemminger <stephen@networkplumber.org>
To: Phil Sutter <phil@nwl.cc>
Cc: Stephen Hemminger <shemming@Brocade.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [iproute PATCH v2] ip-address.8: Document autojoin flag
Date: Wed, 20 Jul 2016 12:22:56 -0700 [thread overview]
Message-ID: <20160720122256.0b7a48a7@xeon-e3> (raw)
In-Reply-To: <7a471e4823c94189afee7f60c1cba183@HQ1WP-EXMB11.corp.brocade.com>
On Tue, 12 Jul 2016 07:56:16 +0000
Phil Sutter <phil@nwl.cc> wrote:
> Description copied from related kernel support commit message with a
> little tailoring to fit.
>
> While at it, fix font of non-terminal CONFFLAG-LIST in synopsis.
>
> Signed-off-by: Phil Sutter <phil@nwl.cc>
Applied
prev parent reply other threads:[~2016-07-20 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-09 10:14 [iproute PATCH] ip-address.8: Document autojoin flag Phil Sutter
2016-07-12 7:56 ` [iproute PATCH v2] " Phil Sutter
[not found] ` <7a471e4823c94189afee7f60c1cba183@HQ1WP-EXMB11.corp.brocade.com>
2016-07-20 19:22 ` 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=20160720122256.0b7a48a7@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).