All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvm-1.0.1-rc4 and 2.4.13
Date: Mon Oct 29 02:59:08 2001	[thread overview]
Message-ID: <20011029084424.D4182@tykepenguin.com> (raw)
In-Reply-To: <20011026213005.C928@sky.net>; from U.Wiederhold@gmx.net on Fri, Oct 26, 2001 at 09:30:05PM +0200

On Fri, Oct 26, 2001 at 09:30:05PM +0200, Ulrich Wiederhold wrote:
> * Patrick Caulfield <caulfield@sistina.com> [011026 10:56]:
> > On Fri, Oct 26, 2001 at 12:54:05AM +0200, Ulrich Wiederhold wrote:
> 
> Two questions:
> 1. Why isn´t lvm-1.0.1-rc4 in the current Linux-Kernel? Why do I still
> need to patch? I think this version is already stable and better than
> the older one, isn´t it?

It just isn't :-( we've submitted (most of) it to Alan Cox and his kernel is
*much* more up-to-date than Linus'. I don't know just why the patches haven't
been accepted by Linus. He is apparently happy to completely replace the VM but
won't fix some fairly serious bugs elsewhere...bizarre.

> 2. Should I write a bug-report to the xfs-guys? If yes, can I include
> your Email, Patrick?

I wouldn't like to claim it's an XFS bug as I haven't had a close look at their
patches. I do know that they include some LVM patches in their distribution so
it's certainly worth asking them nicely to upgrade them I suppose.

Feel free to quote my email..I don't think I wrote anything actionable :-)

patrick

  reply	other threads:[~2001-10-29  2:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-25 17:52 [linux-lvm] lvm-1.0.1-rc4 and 2.4.13 Ulrich Wiederhold
2001-10-26  3:59 ` Patrick Caulfield
2001-10-26 14:27   ` Ulrich Wiederhold
2001-10-29  2:59     ` Patrick Caulfield [this message]
2001-10-29  4:05       ` Ulrich Wiederhold
2001-10-29  4:52         ` GCS
2001-11-03  4:21       ` Paul Dickson

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=20011029084424.D4182@tykepenguin.com \
    --to=caulfield@sistina.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.