Linux LVM users
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Kernel-2.4.15pre6
Date: Tue Nov 20 12:36:01 2001	[thread overview]
Message-ID: <20011120113720.S1308@lynx.no> (raw)
In-Reply-To: <20011120161418.C807@tykepenguin.com>; from caulfield@sistina.com on Tue, Nov 20, 2001 at 04:14:18PM +0000

On Nov 20, 2001  16:14 +0000, Patrick Caulfield wrote:
> On Mon, Nov 19, 2001 at 11:12:18AM -0800, Petro wrote:
> > > If you want to do snapshots of reiserfs (and, I think, ext3) then
> > > you will still need the VFS lock patch yes.
> > 
> >     Is there any indication that this patch will make it in to the
> >     official kernel at some point? 
> 
> I don't know is the honest answer. It's Chris Mason's patch, we just
> distribute it for convenience of LVM users, I don't know if (or how many
> times!) he's tried to submit it for inclusion.

A couple of times, I think.  It may be that it didn't go in the last time
because of the "block-device-in-pagecache" fallout, and VM changes keeping
Linus busy.  I think Marcello will get a _huge_ backlog of patches sent at
him.  Whether this will mean it is easier or harder to get changes in, I
don't know (he may want to stay in "maintenance mode" only, and push all
changes to 2.5 kernels, but hopefully not for well tested changes like this).

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/

      reply	other threads:[~2001-11-20 12:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-18  1:18 [linux-lvm] Kernel-2.4.15pre6 Petro
2001-11-19  2:34 ` Patrick Caulfield
2001-11-19 13:10   ` Petro
2001-11-20 10:13     ` Patrick Caulfield
2001-11-20 12:36       ` Andreas Dilger [this message]

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=20011120113720.S1308@lynx.no \
    --to=adilger@turbolabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox