From: Andi Kleen <ak@muc.de>
To: "David S. Miller" <davem@davemloft.net>
Cc: glen.turner@aarnet.edu.au, netdev@oss.sgi.com, mtk-lkml@gmx.net
Subject: Re: network manpages was Re: is UDP_CORK "real"
Date: 29 Apr 2005 17:29:39 +0200
Date: Fri, 29 Apr 2005 17:29:39 +0200 [thread overview]
Message-ID: <20050429152939.GB38331@muc.de> (raw)
In-Reply-To: <20050427114323.53e43e32.davem@davemloft.net>
On Wed, Apr 27, 2005 at 11:43:23AM -0700, David S. Miller wrote:
> On 27 Apr 2005 14:26:48 +0200
> Andi Kleen <ak@muc.de> wrote:
>
> > It would be nice of course if David could enforce a policy
> > to require a manpage patch for new ioctls/socket options etc.
> > in the future, then such documentation lag would not happen.
>
> I could easily do this if the files were in the kernel tree
> itself, but since it's external it's not so easy to do.
Hmm, you could ask them at least to submit a patch.
>
> Why don't we put them into the kernel tree? They are just
> small documents and I bet they will stay in sync better if
> they were moved into the kernel tree.
Well, you have to talk to Michael who maintains them now.
I personally think it would be a good idea, yes.
-Andi
prev parent reply other threads:[~2005-04-29 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 23:14 is UDP_CORK "real" Rick Jones
2005-04-21 23:25 ` David S. Miller
2005-04-21 23:53 ` Rick Jones
2005-04-26 13:40 ` Andi Kleen
2005-04-27 8:20 ` Michael Kerrisk
[not found] ` <426F2A1D.10001@aarnet.edu.au>
2005-04-27 12:26 ` network manpages was " Andi Kleen
2005-04-27 18:43 ` David S. Miller
2005-04-29 15:29 ` Andi Kleen [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=20050429152939.GB38331@muc.de \
--to=ak@muc.de \
--cc=davem@davemloft.net \
--cc=glen.turner@aarnet.edu.au \
--cc=mtk-lkml@gmx.net \
--cc=netdev@oss.sgi.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).