From: Christoph Hellwig <hch@caldera.de>
To: linux-lvm@sistina.com
Cc: linux-kernel@sistina.com, mge@sistina.com
Subject: Re: [linux-lvm] LVM 1.0 release decision
Date: Fri, 11 May 2001 17:02:26 +0200 [thread overview]
Message-ID: <20010511170226.A20533@caldera.de> (raw)
In-Reply-To: <20010511155311.A17689@sistina.com>; from Mauelshagen@sistina.com on Fri, May 11, 2001 at 03:53:11PM +0000
On Fri, May 11, 2001 at 03:53:11PM +0000, Heinz J. Mauelshagen wrote:
> 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)?
IMHO you should get out a 0.9.1final and sync the stock kernel before...
If and only IF 1.0 will change the IOP again I don't want to see it all
in stock 2.4.0 - the stable series should stay backward compatible.
Otherwise: just relese 1.0 and send the diffs to Alan and Linus - if
they think you changes are ok they will merge it.
Vendors interested in having 1.0 in their kernels will put it in anyway.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2001-05-11 15:02 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 [this message]
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
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=20010511170226.A20533@caldera.de \
--to=hch@caldera.de \
--cc=linux-kernel@sistina.com \
--cc=linux-lvm@sistina.com \
--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