public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-kernel@vger.kernel.org
Cc: mge@sistina.com
Subject: LVM 1.0 release decision
Date: Fri, 11 May 2001 16:27:45 +0000	[thread overview]
Message-ID: <20010511162745.B18341@sistina.com> (raw)


As most of you probably know, we've got criticism a couple of weeks ago about
our Linux kernel patch policy causing the LVM vanilla kernel code to differ
from the one we release directly.

In order to avoid this difference we provide smaller patches more often now.
We have started already with a subset of about 50 necessary patches.

Even though we get kind support from Alan Cox to get those QAed and integrated,
the pure amount of patches will take at least a couple of weeks to make it in.

This leads to the dilemma, that trying to avoid further differences between
our LVM releases and the stock kernel code would force us into postponing
the pending LVM 1.0 release accordingly which OTOH is incovenient for the LVM
user base.

In regard to this situation we'ld like to know about your oppinion on
the following request:
is it acceptable to release 1.0 soon *before* all patches to reach the 1.0 code
status are in vanilla (presumed that we provide them with our release as we
always did before)?

We'll gather your answers for some days and will send the conclusion
to the lists.

Thanks for your support!

-- 

Regards,
Heinz    -- The LVM Guy --

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

             reply	other threads:[~2001-05-11 14:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-11 16:27 Heinz J. Mauelshagen [this message]
2001-05-11 14:32 ` LVM 1.0 release decision Alan Cox
2001-05-11 15:11   ` Andrea Arcangeli
2001-05-11 20:12     ` David S. Miller
2001-05-12  1:24       ` Andrea Arcangeli
2001-05-12  1:29         ` David S. Miller
2001-05-12  2:54           ` Andrea Arcangeli
2001-05-12  5:19             ` David S. Miller
2001-05-12 13:39               ` Andrea Arcangeli
2001-05-13 17:36         ` David Woodhouse
2001-05-13 18:39           ` Alan Cox
2001-05-13 23:17             ` Chris Wedgwood
2001-05-13 19:25           ` Christoph Hellwig
2001-05-11 15:42   ` H. Peter Anvin
2001-05-11 17:02   ` Andreas Dilger
2001-05-16 15:03   ` Heinz J. Mauelshagen
2001-05-16 23:38     ` Alan Cox
2001-05-11 14:39 ` Jeff Garzik
2001-05-11 14:48   ` Mark Hahn

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=20010511162745.B18341@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mge@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