From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [linux-lvm] LVM 1.0 release decision
Date: Wed, 16 May 2001 11:19:03 +0000 [thread overview]
Message-ID: <20010516111903.E11984@sistina.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0105132046150.5468-100000@imladris.rielhome.conectiva>; from riel@conectiva.com.br on Sun, May 13, 2001 at 08:48:19PM -0300
On Sun, May 13, 2001 at 08:48:19PM -0300, Rik van Riel wrote:
> On Fri, 11 May 2001, Steven Lembark wrote:
>
> > for my part running the system i'd rather have the "production"
> > LVM and kernel releases in sync and not have to worry about it.
> > if i need a beta/inter-version release then i'll deal with the
> > extra issues.
>
> Agreed. If the in-kernel LVM cannot be trusted, I really
> don't see why Sistina would ever want to associate its name
> with something broken?
Rik, that's not an issue at all and sorry, it doesn't help either!
With the help of community contributors we *do* provide the most recent
code with as few bugs as possible at www.sistina.com/lvm as we always did.
Everybody could and can get it from there and established LVM users continue
to do it this way.
OTOH we need a lot of time now to get smaller patches into vanilla.
Therefore we kindly asked for community oppinions to help the situation.
Unless a bigger LVM patch to vanilla is accepted, we need to spend a lot of work
on providing those smaller chunks of patches which distracts us a lot from
other work.
Don't tell me that this is all our fault;
this wouldn't *help* to fasten the process either!
A little trust to accept a bigger patch *and* to sort pending issues
out with the help of the community afterwards is a valid approach IMO to
get faster to the point of an updated vanilla LVM driver than with the
tiny patches approach.
Linus, Alan et al.: maybe you could think about it again and
accept one larger LVM patch. Thanks.
>
> I think it would be better for everyone (users, Sistina's
> corporate image and Linux) to get something stable into the
> kernel before sending out the press release ;)
>
> (after all, a version number change is just a one-liner patch
> away ;))
>
> regards,
>
> Rik
> --
> Virtual memory is like a game you can't win;
> However, without VM there's truly nothing to lose...
>
> http://www.surriel.com/ http://distro.conectiva.com/
>
> Send all your spam to aardvark@nl.linux.org (spam digging piggy)
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2001-05-16 11:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 15:53 [linux-lvm] LVM 1.0 release decision Heinz J. Mauelshagen
2001-05-11 14:06 ` Adrian Phillips
2001-05-11 16:26 ` Heinz J. Mauelshagen
2001-05-11 14:13 ` Torsten Landschoff
2001-05-16 11:23 ` Heinz J. Mauelshagen
2001-05-11 14:22 ` Terje Kvernes
2001-05-17 8:08 ` Harald Milz
2001-05-17 20:11 ` Terje Kvernes
2001-05-11 15:02 ` Christoph Hellwig
2001-05-11 17:41 ` Jorg de Jong
2001-05-11 19:52 ` Steven Lembark
2001-05-13 23:48 ` Rik van Riel
2001-05-16 11:19 ` Heinz J. Mauelshagen [this message]
2001-05-16 15:23 ` Chad C. Walstrom
2001-05-16 15:42 ` Rik van Riel
2001-05-16 16:35 ` Steven Lembark
2001-05-16 16:33 ` Steven Lembark
2001-05-11 20:36 ` Jos� Luis Domingo L�pez
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=20010516111903.E11984@sistina.com \
--to=mauelshagen@sistina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lvm@sistina.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