From: "Fernando Alencar Maróstica" <famarost@unimep.br>
To: David Weinehall <tao@acc.umu.se>
Cc: fadel@ferasoft.com.br, linux-kernel@vger.kernel.org
Subject: [PATCH 2.0] Fixed kernel stuff
Date: 15 Oct 2002 13:37:25 -0200 [thread overview]
Message-ID: <1034696247.823.118.camel@nitrogenium> (raw)
In-Reply-To: <20021014220527.GU26715@khan.acc.umu.se>
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 ...
Please apply.
best regards,
--
Fernando Alencar Maróstica
Graduate Student, Computer Science
Linux Register User Id #281457
University Methodist of Piracicaba
Departament of Computer Science
home: http://www.unimep.br/~famarost
next parent reply other threads:[~2002-10-15 16:27 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 [this message]
2002-10-15 19:02 ` [PATCH 2.0] Fixed kernel stuff Fernando Alencar Maróstica
2002-10-15 21:11 ` David Weinehall
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=1034696247.823.118.camel@nitrogenium \
--to=famarost@unimep.br \
--cc=fadel@ferasoft.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=tao@acc.umu.se \
/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.