Date: Wed, 20 Oct 2004 22:00:37 -0700
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
Message-Id: <20041020220037.2e209907.akpm@osdl.org>
In-Reply-To: <41773D3F.2040801@verizon.net>
References: <4176CFE3.2030306@verizon.net>
	<20041020153058.6de41ed8.akpm@osdl.org>
	<4176EBD8.3050306@verizon.net>
	<20041021042036.GB14189@redhat.com>
	<41773D3F.2040801@verizon.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1370
Lines: 34

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.
-
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/