public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Louis Garcia <louisg00@bellsouth.net>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: future of rmap VM
Date: 16 Feb 2002 16:29:23 -0500	[thread overview]
Message-ID: <1013894969.1283.8.camel@tiger> (raw)
In-Reply-To: <Pine.LNX.4.33L.0202072006010.17850-100000@imladris.surriel.com>
In-Reply-To: <Pine.LNX.4.33L.0202072006010.17850-100000@imladris.surriel.com>

When do you plan to have a complete rmap VM ready for general use? Whats left to do?

Also, have you discussed merging this VM into the mainline kernel, either 2.4 or 2.5?

To me, this VM is far better than the current VM.

--Louis


  parent reply	other threads:[~2002-02-16 21:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-07 20:40 Problem with rmap-12c Louis Garcia
2002-02-07 22:12 ` Rik van Riel
2002-02-07 22:32   ` Shawn Starr
2002-02-07 23:30     ` Rik van Riel
2002-02-08 21:06   ` Louis Garcia
2002-02-08 21:30     ` Rik van Riel
2002-02-16 21:29   ` Louis Garcia [this message]
2002-02-16 21:41     ` future of rmap VM Rik van Riel

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=1013894969.1283.8.camel@tiger \
    --to=louisg00@bellsouth.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    /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