All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Diego Calleja <diegocg@gmail.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, nathans@sgi.com,
	davem@davemloft.net
Subject: Re: [RFC] Update sysctl documentation
Date: Tue, 06 Jun 2006 09:53:41 -0400	[thread overview]
Message-ID: <448588E5.1070702@rtr.ca> (raw)
In-Reply-To: <20060606035833.bee909af.diegocg@gmail.com>

> As I promised, I've updated all the documentation concerning sysctls.
> 
> First of all: the formatting I've choosen is to recreate the structure
> of /proc/sys/* and put the documentation for every value in a separated
> file,

Thanks for doing this.  But I must say, having a zillion tiny little
files makes it very difficult to browse the documentation.

Perhaps one file per subdirectory or subsystem?  That way, related values
stay together and the end-user of the documentation can figure it out easier.

Cheers

      parent reply	other threads:[~2006-06-06 13:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06  1:58 [RFC] Update sysctl documentation Diego Calleja
2006-06-06  3:28 ` Bernd Eckenfels
2006-06-06 13:29   ` Diego Calleja
2006-06-06 13:53 ` Mark Lord [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=448588E5.1070702@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=diegocg@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathans@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.