From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] the big Documentation/Changes change
Date: Tue, 9 Aug 2005 20:38:17 -0700 [thread overview]
Message-ID: <20050809203817.2225a33f.rdunlap@xenotime.net> (raw)
In-Reply-To: <20050810011740.GR4006@stusta.de>
On Wed, 10 Aug 2005 03:17:40 +0200 Adrian Bunk wrote:
> I edited Documentation/Changes:
> - remove obsolete information
> - point to feature-list-2.6.txt instead of providing similar information
> - removed the URLs of the software packages (people compiling their own
> kernel usually know where to find the required software)
I always found those real handy.
Overall, I find this a good idea.
> The resulting file is pretty short.
> Documentation/Changes | 376 +-----------------------------------------
> 1 files changed, 15 insertions(+), 361 deletions(-)
>
> --- linux-2.6.13-rc5-mm1-full/Documentation/Changes.old 2005-08-10 03:01:11.000000000 +0200
> +++ linux-2.6.13-rc5-mm1-full/Documentation/Changes 2005-08-10 03:12:12.000000000 +0200
> @@ -1,435 +1,89 @@
> -Kernel compilation
> -==================
> +Notes
> +=====
> +
> +Please read feature-list-2.6.txt for information about new features
We usually prefix Doc file names with Documentation/, even though
this is in the same directory.
but where is this file? I can't find it.
Ah, it's in -mm only.
> +and changes compared to 2.4 kernels.
---
~Randy
next prev parent reply other threads:[~2005-08-10 3:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-10 1:17 Adrian Bunk
2005-08-10 3:38 ` Randy.Dunlap [this message]
2005-08-20 3:45 ` Adrian Bunk
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=20050809203817.2225a33f.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=bunk@stusta.de \
--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
all inboxes | Powered by JetHome®