From: Jim Nelson <james4765@verizon.net>
To: Dave Jones <davej@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Structural changes for Documentation directory
Date: Thu, 21 Oct 2004 05:43:24 -0400 [thread overview]
Message-ID: <417784BC.1060707@verizon.net> (raw)
In-Reply-To: <20041021050528.GA26814@redhat.com>
Dave Jones wrote:
> On Wed, Oct 20, 2004 at 10:00:37PM -0700, Andrew Morton wrote:
> > > The other possibility is to have a TODO file with a list of out-of-date
> > > files, and have the removal of the file listing in the TODO file be part
> > > of the patch submission.
> >
> > It all sounds too complex. ./docs/ is fine.
>
> asides from bloating up interdiffs, what does moving stuff around
> gain us over just fixing stuff in place ? Do we really have
> that much out of date documentation to justify this ?
>
> Dave
>
>
Well, before I started this thread, I actually looked through the root
Documentation directory, taking notes, and there were 40 files that were
definitely out of date, and 10 that were not obviously out of date, but
had no indication that it had been updated recently.
That's without digging into the subdirectories.
Jim
prev parent reply other threads:[~2004-10-21 11:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 20:51 [RFC] Structural changes for Documentation directory Jim Nelson
2004-10-20 22:23 ` Nigel Cunningham
2004-10-20 22:44 ` Måns Rullgård
2004-10-20 22:30 ` Andrew Morton
2004-10-20 22:51 ` Jim Nelson
2004-10-21 4:20 ` Dave Jones
2004-10-21 4:38 ` Jim Nelson
2004-10-21 5:00 ` Andrew Morton
2004-10-21 5:05 ` Dave Jones
2004-10-21 5:07 ` Andrew Morton
2004-10-21 9:43 ` Jim Nelson [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=417784BC.1060707@verizon.net \
--to=james4765@verizon.net \
--cc=akpm@osdl.org \
--cc=davej@redhat.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