From: walter harms <wharms@bfs.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] another potential KJ project -- cleaning out Documentation/
Date: Sun, 04 Feb 2007 16:35:52 +0000 [thread overview]
Message-ID: <45C60B68.6000405@bfs.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0702040437130.26073@CPE00045a9c397f-CM001225dbafb6>
Robert P. J. Day wrote:
> not sure if this is a viable project, but it strikes me that there's
> a *heap* of stuff in the current 2.6 Documentation/ directory that
> could be either reorganized, updated or outright deleted. and, in
> this case, deletion of outdated content *would* have its value since
> out-of-date documentation can be annoyingly misleading and a real time
> waster.
>
> in terms of reorganization, i think it would be nice to see more of
> a hierarchical structure. for example, i can imagine a single
> "debugging" directory with all debugging-related text files.
>
> perhaps another one called "developers" which would contain
> everything related to submitting patches and drivers, and the
> submission checklist, etc, etc. you get the idea.
>
> and in terms of outright deletion, not to pick on any one
> architecture but just grabbing something at random, there's a "cris"
> directory with a single README file for its contents, that begins:
>
> Linux 2.4 on the CRIS architecture
> =================
> $Id: README,v 1.7 2001/04/19 12:38:32 bjornw Exp $
> ...
>
> if this really is 2.4-specific content, its value in the 2.6.20 kernel
> tree is fairly low, if not non-existent.
>
> anyway, thoughts? there's a lot of valuable info in the
> Documentation/ directory, but it seems to be getting increasingly
> buried under aging and obsolete content.
>
> rday
>
This CRIS processor is supported also with the 2.6 architecture.
re,
wh
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2007-02-04 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-04 9:43 [KJ] another potential KJ project -- cleaning out Documentation/ Robert P. J. Day
2007-02-04 16:35 ` walter harms [this message]
2007-02-04 18:04 ` Robert P. J. Day
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=45C60B68.6000405@bfs.de \
--to=wharms@bfs.de \
--cc=kernel-janitors@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.