From: Diego Calleja <diegocg@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Update/kill Documentation/sysctl/* docs?
Date: Thu, 11 May 2006 13:56:47 +0200 [thread overview]
Message-ID: <20060511135647.973d339e.diegocg@gmail.com> (raw)
In-Reply-To: <20060510233728.5c27cc43.akpm@osdl.org>
El Wed, 10 May 2006 23:37:28 -0700,
Andrew Morton <akpm@osdl.org> escribió:
> I'd have thought that keeping everything in Documentation/sysctl/*.txt and
> killing proc.txt would be the best approach?
>
> But I haven't looked into it much. You have - what approach are you
> recommending?
Well, filesystems/proc.txt is somewhat more updated than sysctl/* - 2.4
vs 2.2 (sic) (and some small 2.6 updates spread in both places). However,
filesystems/* should only contain IMO docs about the filesystem themselves
not about the data in the filesystems, and proc.txt only documents
sysctls, nothing else.
So I guess the Right Thing would be to move proc.txt to
Documentation/sysctl, and use e-violence to make people update the
non-documented parts ;) (And apparently there's more sysctl stuff lost
in the noise like networking/ip-sysctl.txt, etc)
I'll try to move everything to sysctl/ and will post a RFC about it.
(Wouldn't have sense to have a Documentation/sysfs directory documenting
the sysfs interfaces aswell?)
next prev parent reply other threads:[~2006-05-11 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 22:48 [RFC] Update/kill Documentation/sysctl/* docs? Diego Calleja
2006-05-11 6:37 ` Andrew Morton
2006-05-11 11:56 ` Diego Calleja [this message]
2006-05-11 14:26 ` Andrew Morton
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=20060511135647.973d339e.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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