From: "Dominic J. Eidson" <sauron@the-infinite.org>
To: Linux-LVM <linux-lvm@msede.com>
Subject: [linux-lvm] Modification to the LVM Petition...
Date: Thu, 2 Sep 1999 18:33:27 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.05.9909021823250.12355-100000@morannon.kdi.com> (raw)
Sorry for being so post-happy today, I promise I will go back to being a
lurker after this :)
I have updated the LVM Petition page, to try to correct for LWN's
misconceptions. Currently, the top part of the page (before the PRO/CON's)
reads:
"As the Linux LVM matures, interest to have it included into the stable
Linux kernel, increases. Currently, Alan Cox has added LVM to the
2.2.10-ac? and 2.2.11-ac? patches, however we are interested in
getting LVM into the main 2.3.x kernels, and hopefully the upcoming
2.4 kernel(s). Heinz Mauelshagen inquired about this, and heard back
that Linus wanted to wait before putting LVM into the kernel to see if
enough people were interested. In order to facilitate this, we've
opted to try to convince the supporters of LVM in the Linux kernel to
sign a petition, which we then can present to Linus Torvalds, to show
how people are indeed interested in seeing Linux finally have a LVM."
There is also a reference link pointing to Heinz's post where he heard
from Dirk Hohndel about Linus wanting to wait.. (In addition to the 2
links already present, the first being to http://linux.msede.com/lvm/, the
other being to the sign-up form at the end of the page).
--
Dominic J. Eidson
"Baruk Khazad! Khazad ai-menu!" - Gimli
--------------------------------------------------------------------------------
http://www.the-infinite.org/ http://www.the-infinite.org/~dominic/
reply other threads:[~1999-09-02 23:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.05.9909021823250.12355-100000@morannon.kdi.com \
--to=sauron@the-infinite.org \
--cc=linux-lvm@msede.com \
/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;
as well as URLs for NNTP newsgroup(s).