From: Chris Mason <mason@suse.com>
To: linux-lvm@sistina.com
Subject: Re: [lvm-devel] Re: [linux-lvm] LVM 0.9 vgscan problem
Date: Fri, 05 Jan 2001 10:22:48 -0500 [thread overview]
Message-ID: <620160000.978708168@tiny> (raw)
In-Reply-To: <Pine.LNX.4.21.0101051308461.1295-100000@duckman.distro.conectiva>
On Friday, January 05, 2001 01:10:22 PM -0200 Rik van Riel
<riel@conectiva.com.br> wrote:
> On Fri, 5 Jan 2001, Heinz J. Mauelshagen wrote:
>
>> Rik, nobody was "sitting" on bugfixes. It just got fixed
>> recently and still needed some testing before making it into
>> 2.4.0.
>
> Ahh I see...
>
>> As I stated in my other email: Andrea Arcangeli's help to
>> integrate 0.9 into 2.4.0 brought it in. TTBOMK there was no
>> previous negotiation about 0.9 inclusion in 2.4.0 with us
>> before :-(
>
> OUCH ... so LVM 0.9 got pushed into the kernel before you
> had a chance to do some serious testing ? ;(
>
Yes and no. I asked Heinz what was needed to include 0.9 on the next suse
release. He gave me a short list of the known huge bugs, I fixed them and
sent the patches along to andrea. Andrea picked up my merging patch into
his tree, but I wasn't clear enough about the bug fix patch and it was
missed.
And, I missed that it didn't get into the kernel until it was too late
(sorry Heinz).
-chris
next prev parent reply other threads:[~2001-01-05 15:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 22:56 [linux-lvm] LVM 0.9 vgscan problem Rik van Riel
2001-01-03 22:56 ` Rik van Riel
2001-01-04 17:49 ` [linux-lvm] " Rik van Riel
2001-01-04 22:01 ` [lvm-devel] " Rik van Riel
2001-01-05 11:38 ` Jan Niehusmann
2001-01-05 11:57 ` Rik van Riel
2001-01-05 15:34 ` Heinz J. Mauelshagen
2001-01-05 15:10 ` Rik van Riel
2001-01-05 15:22 ` Chris Mason [this message]
2001-01-05 3:56 ` Paul Jakma
2001-01-05 15:29 ` Heinz J. Mauelshagen
2001-01-05 15:27 ` Paul Jakma
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=620160000.978708168@tiny \
--to=mason@suse.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.