From: Stephen Hemminger <shemminger@vyatta•com>
To: Hagen Paul Pfeifer <hagen@jauu•net>
Cc: netdev@vger•kernel.org
Subject: Re: [RFC] iproute2: split up ip man page?
Date: Thu, 22 Dec 2011 16:29:59 -0800 [thread overview]
Message-ID: <20111222162959.167b9df0@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <20111223001003.GD4767@hell>
On Fri, 23 Dec 2011 01:10:03 +0100
Hagen Paul Pfeifer <hagen@jauu•net> wrote:
> * Stephen Hemminger | 2011-12-22 10:37:23 [-0800]:
>
> >Ok, the ip man page is now broken up. I tried to fix some of the
> >incorrect grammar and usage as well. The pages still need editing for
> >readability.
>
> Great! Commit 1b1177ed5f3 synched kernel headers. Should I rebase my iproute
> netem rate patch (and again update include/linux/pkt_sched.h for net-next) or
> keep you aware of this?
>
> Hagen
I am fixing netem loss stuff now. Fixing broken gimodel.
After 3.2 is released, the will merge in support for 3.3 features.
next prev parent reply other threads:[~2011-12-23 0:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 21:15 [RFC] iproute2: split up ip man page? Stephen Hemminger
2011-12-07 21:46 ` Ben Hutchings
2011-12-08 9:15 ` Petr Šabata
2011-12-22 18:37 ` Stephen Hemminger
2011-12-23 0:10 ` Hagen Paul Pfeifer
2011-12-23 0:29 ` Stephen Hemminger [this message]
2011-12-23 11:57 ` Hagen Paul Pfeifer
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=20111222162959.167b9df0@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta$(echo .)com \
--cc=hagen@jauu$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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