All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Thornber <thornber@btconnect.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Why aren't the linux-sources up to date?
Date: Fri, 31 Aug 2001 13:47:17 +0100	[thread overview]
Message-ID: <20010831134717.A585@btconnect.com> (raw)
In-Reply-To: <OF41C775E9.837668B1-ONC1256AB9.002E0C80@gillette.com>; from Daniel_Schroeter@gillette.com on Fri, Aug 31, 2001 at 10:31:07AM +0200

On Fri, Aug 31, 2001 at 10:31:07AM +0200, Daniel_Schroeter@gillette.com wrote:
> Hi LVM-team,
> we're testing the LVM in the company. I using the kernel 2.4.9. Why don't
> have the sources from the linux-kernel the current LVM version (1.0.1)? I
> need to patch the sources with your makefile. Yes, it works fine :-)
> 
> I writing a articel for the company, so I need the information why, the
> current linux kernel, doesn't have the newest LVM version.
> Thank's for a answer of this question.

Good question.  

Alan Cox has integrated patches up to Beta 7.  Currently he's waiting
for me to send the final patch set which will bring him up to date with
1.0.1, I'm waiting until I'm confident the changes are correct.

Linus' kernels contain beta2 level code.  I can only assume that Alan
has pushed the patches forward to Linus and they have been rejected.
There *are* issues with the driver, regarding the ioctl interface
among other things.  But in the short term I feel it would be better
if Linus were to accept the patches from Alan since beta2 was quite
broken.

- Joe

  parent reply	other threads:[~2001-08-31 12:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-31  8:31 [linux-lvm] Why aren't the linux-sources up to date? Daniel_Schroeter
2001-08-31 12:29 ` Goetz Bock
2001-08-31 12:47 ` Joe Thornber [this message]
2001-08-31 15:28   ` Jan Niehusmann

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=20010831134717.A585@btconnect.com \
    --to=thornber@btconnect.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.