From: William Lee Irwin III <wli@holomorphy.com>
To: Kirk True <kirktrue@pacbell.net>
Cc: kernelnewbies <kernelnewbies@nl.linux.org>, Linux-MM@kvack.org
Subject: Re: Fixing VM bugs?
Date: Wed, 25 Aug 2004 21:25:43 -0700 [thread overview]
Message-ID: <20040826042543.GN2793@holomorphy.com> (raw)
In-Reply-To: <412D636B.2080109@pacbell.net>
On Wed, Aug 25, 2004 at 09:13:31PM -0700, Kirk True wrote:
> I'd like to try fixing bugs as a way to get more familiar with the VM
> code. Is there a list of known/outstanding bugs that need to be fixed?
> Is http://bugme.osdl.org the place to go or somewhere else? I mean I see
> VM patches posted most everyday but I haven't really found the *source*
> of the patches - are they bug fixes for issues other people found or
> just issues the VM hackers noticed themselves?
Most known VM issues are likely design flaws. Pure bugfixing work would
consist of finding the bugs in addition to writing fixes.
-- wli
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
prev parent reply other threads:[~2004-08-26 4:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 4:13 Fixing VM bugs? Kirk True
2004-08-26 4:25 ` William Lee Irwin III [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=20040826042543.GN2793@holomorphy.com \
--to=wli@holomorphy.com \
--cc=Linux-MM@kvack.org \
--cc=kernelnewbies@nl.linux.org \
--cc=kirktrue@pacbell.net \
/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.