From: Stephen Hemminger <stephen@networkplumber.org>
To: Simon Horman <simon.horman@netronome.com>
Cc: netdev@vger.kernel.org
Subject: Re: RFC iproute2 doc files
Date: Fri, 29 Sep 2017 10:28:47 -0700 [thread overview]
Message-ID: <20170929102847.224dbd08@xeon-e3> (raw)
In-Reply-To: <20170928071803.GA15815@netronome.com>
On Thu, 28 Sep 2017 09:18:04 +0200
Simon Horman <simon.horman@netronome.com> wrote:
> On Wed, Sep 20, 2017 at 08:11:59AM -0700, Stephen Hemminger wrote:
> > I noticed that the iproute man pages are up to date but the LaTex documentation
> > is very out of date. Rarely updated since the Linux 2.2 days.
> >
> > Either someone needs to do a massive editing job on them, or they should just
> > be dropped. My preference would be to just drop everything in the doc/ directory.
> > The current versions are so old, they can't be helping.
>
> FWIW, removing stale documentation sounds sensible to me.
I removed all the stale ones. The file ip-cref was occasionally updated.
next prev parent reply other threads:[~2017-09-29 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 15:11 RFC iproute2 doc files Stephen Hemminger
2017-09-28 7:18 ` Simon Horman
2017-09-29 17:28 ` Stephen Hemminger [this message]
2017-10-02 7:31 ` Leon Romanovsky
2017-10-02 14:56 ` 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=20170929102847.224dbd08@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@netronome.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.