netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Sutter <phil@nwl.cc>
To: Thomas Haller <thaller@redhat.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] man: fix documentation for range of route table ID
Date: Thu, 21 Sep 2017 20:26:47 +0200	[thread overview]
Message-ID: <20170921182647.GB30364@orbyte.nwl.cc> (raw)
In-Reply-To: <20170921181411.17720-1-thaller@redhat.com>

On Thu, Sep 21, 2017 at 08:14:11PM +0200, Thomas Haller wrote:
> Signed-off-by: Thomas Haller <thaller@redhat.com>

Fixes: 4ec1933dfddfc ("Update ip.8 man page to describe route table id values")

(So that bug is over 7 years old. :)

Cheers, Phil

  reply	other threads:[~2017-09-21 18:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21 18:14 [PATCH iproute2] man: fix documentation for range of route table ID Thomas Haller
2017-09-21 18:26 ` Phil Sutter [this message]
2017-09-22 11:28   ` [PATCH iproute2 v2] " Thomas Haller
2017-09-22 17:09     ` Stephen Hemminger

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=20170921182647.GB30364@orbyte.nwl.cc \
    --to=phil@nwl.cc \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    --cc=thaller@redhat.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).