From: Adrian Bunk <bunk@stusta.de>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [patch 2.6.13-rc6] docs: fix misinformation about overcommit_memory
Date: Sat, 20 Aug 2005 12:56:55 +0200 [thread overview]
Message-ID: <20050820105654.GO3615@stusta.de> (raw)
In-Reply-To: <200508192318_MC3-1-A7AE-1D7A@compuserve.com>
On Fri, Aug 19, 2005 at 11:14:39PM -0400, Chuck Ebbert wrote:
> Someone complained about the docs for vm_overcommit_memory being wrong.
> This patch copies the text from the vm documentation into procfs.
> Please apply.
>...
Do we really need two copies of the same text?
Couldn't you instead write some kind of "please look at
Documentation/vm/overcommit-accounting"?
> Chuck
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-08-20 10:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-20 3:14 [patch 2.6.13-rc6] docs: fix misinformation about overcommit_memory Chuck Ebbert
2005-08-20 3:24 ` Andrew Morton
2005-08-20 10:56 ` Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-20 7:07 Chuck Ebbert
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=20050820105654.GO3615@stusta.de \
--to=bunk@stusta.de \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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