public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Diego Calleja <diegocg@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Update/kill Documentation/sysctl/* docs?
Date: Wed, 10 May 2006 23:37:28 -0700	[thread overview]
Message-ID: <20060510233728.5c27cc43.akpm@osdl.org> (raw)
In-Reply-To: <20060509004837.d542d2d8.diegocg@gmail.com>

Diego Calleja <diegocg@gmail.com> wrote:
>
> In http://bugzilla.kernel.org/show_bug.cgi?id=6145 you asked to update
>  the sysctl docs. I've updated them and added/deleted the neccesary
>  stuff (except the ones that I don't know what on earth are they doing
>  because they're not...documented).

OK..

> However it looks like there's
>  duplication - Documentation/filesystems/proc.txt seems to document all
>  that aswell (but in a single doc, which makes it a bit unreadable 
>  for such big document, IMO)

Yes, the duplication is silly and wasteful and error-inducing.

>  What should be the best step? Kill Documentation/sysctl/ and keep 
>  filesystems/proc.txt updated and maybe split it in several files
>  to make it more readable? Update it but maintain in sync with
>  filesystems/proc.txt? delete proc.txt and keep sysctl/ updated...?

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?

  reply	other threads:[~2006-05-11  6:40 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 [this message]
2006-05-11 11:56   ` Diego Calleja
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=20060510233728.5c27cc43.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=diegocg@gmail.com \
    --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