From: "David S. Miller" <davem@davemloft.net>
To: Andi Kleen <ak@muc.de>
Cc: glen.turner@aarnet.edu.au, netdev@oss.sgi.com
Subject: Re: network manpages was Re: is UDP_CORK "real"
Date: Wed, 27 Apr 2005 11:43:23 -0700 [thread overview]
Message-ID: <20050427114323.53e43e32.davem@davemloft.net> (raw)
In-Reply-To: <20050427122648.GA12597@muc.de>
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.
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.
next prev parent reply other threads:[~2005-04-27 18:43 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 [this message]
2005-04-29 15:29 ` Andi Kleen
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=20050427114323.53e43e32.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ak@muc.de \
--cc=glen.turner@aarnet.edu.au \
--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).