From: Dave Jones <davej@redhat.com>
To: Jim Nelson <james4765@verizon.net>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Structural changes for Documentation directory
Date: Thu, 21 Oct 2004 00:20:36 -0400 [thread overview]
Message-ID: <20041021042036.GB14189@redhat.com> (raw)
In-Reply-To: <4176EBD8.3050306@verizon.net>
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
next prev parent reply other threads:[~2004-10-21 4:31 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 [this message]
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
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=20041021042036.GB14189@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--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 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.