From: Stephen Hemminger <shemminger@osdl.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Updated sysctl documentation take #2
Date: Wed, 7 Jun 2006 12:46:41 -0700 [thread overview]
Message-ID: <20060607124641.516c7fff@localhost.localdomain> (raw)
In-Reply-To: 20060607205316.bbb3c379.diegocg@gmail.com
On Wed, 7 Jun 2006 20:53:16 +0200
Diego Calleja <diegocg@gmail.com> wrote:
> Since people didn't like the "many small files" approach, I've moved
> it to directories containing index.txt files:
>
> Documentation/sysctl/vm/index.txt
> Documentation/sysctl/net/core/index.txt
> Documentation/sysctl/net/unix/index.txt
> Documentation/sysctl/net/ipv4/index.txt
> Documentation/sysctl/net/ipv4/conf/index.txt
> Documentation/sysctl/net/ipv4/route/index.txt
> Documentation/sysctl/net/ipv4/neigh/index.txt
>
> and so on.
>
> As previously, this moves all sysctl documentation (including
> XFS and network) to Documentation/sysctl/*. The patch is
> against linus tree and weights more than 200K in size
> and is place at: http://www.terra.es/personal/diegocg/sysctl-docs
>
> Comments?
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
The network stuff was all in Documentation/networking/ip-sysctl.txt.
Someone else has already started fixing it.
next prev parent reply other threads:[~2006-06-07 19:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 18:53 Updated sysctl documentation take #2 Diego Calleja
2006-06-07 19:46 ` Stephen Hemminger [this message]
2006-06-07 20:55 ` Diego Calleja
2006-06-07 21:24 ` [PATCH] Updated Documentation/networking/ip-sysctl.txt Robert Fitzsimons
2006-06-07 20:06 ` Updated sysctl documentation take #2 Randy.Dunlap
2006-06-07 22:18 ` Diego Calleja
2006-06-11 3:41 ` Randy.Dunlap
2006-06-07 23:56 ` Johannes Stezenbach
2006-06-07 22:52 ` David Lang
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=20060607124641.516c7fff@localhost.localdomain \
--to=shemminger@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 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.