From: Alan Cox <alan@redhat.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Marc-Christian Petersen <m.c.p@kernel.linux-systeme.com>,
linux-kernel@vger.kernel.org, Alan Cox <alan@redhat.com>,
Vincent Lefevre <vincent@vinc17.org>
Subject: Re: [2.4.26] overcommit_memory documentation clarification
Date: Thu, 27 May 2004 17:12:33 -0400 [thread overview]
Message-ID: <20040527211233.GA357@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040527130925.GA13520@logos.cnet>
On Thu, May 27, 2004 at 10:09:25AM -0300, Marcelo Tosatti wrote:
> The strict overcommit fixes need to be extraced and tested.
Bero's tree has them. If you merge it it is probably good to make
the small changes so it works like 2.6
prev parent reply other threads:[~2004-05-27 21:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-09 0:10 [2.4.26] overcommit_memory documentation clarification Vincent Lefevre
2004-05-09 2:04 ` Richard B. Johnson
2004-05-09 2:20 ` Vincent Lefevre
2004-05-09 21:06 ` Paul Jackson
2004-05-09 21:49 ` Vincent Lefevre
2004-05-27 12:20 ` Marcelo Tosatti
2004-05-27 12:30 ` Marc-Christian Petersen
2004-05-27 13:09 ` Marcelo Tosatti
2004-05-27 13:19 ` Dave Jones
2004-05-27 21:12 ` Alan Cox [this message]
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=20040527211233.GA357@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@kernel.linux-systeme.com \
--cc=marcelo.tosatti@cyclades.com \
--cc=vincent@vinc17.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