From: David Weinehall <tao@acc.umu.se>
To: "Fernando Alencar Maróstica" <famarost@unimep.br>
Cc: fadel@ferasoft.com.br, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.0] Fixed kernel stuff
Date: Tue, 15 Oct 2002 23:11:03 +0200 [thread overview]
Message-ID: <20021015211103.GV26715@khan.acc.umu.se> (raw)
In-Reply-To: <1034708558.427.0.camel@nitrogenium>
On Tue, Oct 15, 2002 at 05:02:37PM -0200, Fernando Alencar Maróstica wrote:
> Hello all, specially David
>
> I think this patch is trivial enough to be accepted, but...
>
> This patch fixed some stuff:
> * Fixed warning in script/lxdialog/menubox.c
> * Fixed warning in script/lxdialog/textbox.c
> * Small VM updates ...
Since you are doing changes to the VM, I would like detail descriptions
of what each change does, and why it is necessary, stability- or
security-wise. I will not accept changes to the VM subsystem unless
there is a valid reason; let the early v2.4-series be witness to why
this is a good stance.
Speedups are generally not counted as a valid reason, unless we're
talking a change in the order of a magnitude or more. Code cleanup
might be a good reason, but then I'll merge it into the 2.0.41-tree
instead; this will probably be the case for your lxdialog-fixes, since
I'm cleaning up that code anyway for 2.0.41.
Regards: David Weinehall
--
/> David Weinehall <tao@acc.umu.se> /> Northern lights wander <\
// Maintainer of the v2.0 kernel // Dance across the winter sky //
\> http://www.acc.umu.se/~tao/ </ Full colour fire </
next prev parent reply other threads:[~2002-10-15 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1034548634.543.1.camel@nitrogenium>
[not found] ` <20021014220527.GU26715@khan.acc.umu.se>
2002-10-15 15:37 ` Fernando Alencar Maróstica
2002-10-15 19:02 ` Fernando Alencar Maróstica
2002-10-15 21:11 ` David Weinehall [this message]
2002-10-21 19:49 ` Fernando Alencar Maróstica
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=20021015211103.GV26715@khan.acc.umu.se \
--to=tao@acc.umu.se \
--cc=fadel@ferasoft.com.br \
--cc=famarost@unimep.br \
--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®