[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [linux-lvm] Oops in 2.4.0 (@ LVM)

On Thu, 11 Jan 2001, Heinz J. Mauelshagen wrote:

> It is updated continously.

aye, i know it is.. but not in Linus' tree, and that's the problem.

Linus was given 0.9 by Andrea a good while ago. It has problems. CVS
has had many updates.. but these are not fed to Linus. Not good.
Either keep Linus LVM relatively closely in-sync by feeding to him
frequently, or else feed him /stable/ updates less frequently.

In the former case, users can rely on stock LVM being up to date. In
the latter case users can choose to stick with stock or use CVS. The
current half-way house case means you never really know where you

I'm sorry for complaining, and please read all my 'complain' emails
with an implicit #include "thanks-for-lvm.txt", but....

The release practices of the LVM developers has, to date, /sucked/
(witness pre 0.8.1). I guess you guys (understandably) prefer
spending time on the code over spending time on organising
releases/updates, but the current situation makes life difficult for

Perhaps a solution could be that you (Heinz et al) could delegate to
someone with the technical competance to understand the fixes who
could undertake 'watching' the developers and feeding the fixes on to
Linus? Eg, Andreas did a really good job of maintaining 0.8 fixes (to
tools) until 0.8.1 came out. *cough*

Paul Jakma	paul clubi ie	paul jakma org
PGP5 key: http://www.clubi.ie/jakma/publickey.txt
A Fortran compiler is the hobgoblin of little minis.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]