public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Jim Nelson <james4765@verizon.net>
Cc: davej@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Structural changes for Documentation directory
Date: Wed, 20 Oct 2004 22:00:37 -0700	[thread overview]
Message-ID: <20041020220037.2e209907.akpm@osdl.org> (raw)
In-Reply-To: <41773D3F.2040801@verizon.net>

Jim Nelson <james4765@verizon.net> wrote:
>
> Dave Jones wrote:
>  > On Wed, Oct 20, 2004 at 06:51:04PM -0400, Jim Nelson wrote:
>  > 
>  >  > True.  "./2.6-docs" would reflect the the intent of having 
>  >  > version-specific information, with the "./Documentation" directory left 
>  >  > for general information and files of historical interest.
>  > 
>  > version numbers in directories are nearly always a bad idea,
>  > as they always tend to look a bit silly when the subsequent
>  > release is made.
>  > 
>  > 		Dave
>  > 
>  > 
> 
>  But it would also give a clue that the docs are out of date.  Perhaps 
>  later in each developement cycle, there could be an effort to check the 
>  documentation, with a 2.8-docs or 3.0-docs being the result, and dumping 
>  the 2.6-docs into the historical reference directory.
> 
>  Or, the old stuff could be dropped with the new stable release.
> 
>  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.

  reply	other threads:[~2004-10-21  5:14 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 [this message]
2004-10-21  5:05           ` Dave Jones
2004-10-21  5:07             ` Andrew Morton
2004-10-21  9:43             ` Jim Nelson

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=20041020220037.2e209907.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=james4765@verizon.net \
    --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