From: Chris Mason <mason@suse.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] snapshot of Reiserfs
Date: Wed, 21 Feb 2001 10:34:33 -0500 [thread overview]
Message-ID: <2090960000.982769673@tiny> (raw)
In-Reply-To: <20010221141119.I568@tykepenguin.com>
On Wednesday, February 21, 2001 02:11:20 PM +0000 Patrick Caulfield
<caulfield@sistina.com> wrote:
[ non-intuitive snapshot patches for reiserfs ]
>
>> In fact, why are these separate patches? Shouldn't they
>> eventually be "the standard" and find their way into the
>> stock kernel? It's arguably the correct behavior.
>
> That is the intension. The patch is Chris Mason's and I beleive
> he is trying to get it into the kernel. Heinz emailed him about
> it recently, I don't know if he has had any reply yet.
>
We can probably talk Alan into putting it in the ac series, but I'm not
expecting Linus to take it yet. I'll send it along for 2.4.3preX though
(once 2.4.2 comes out), maybe we'll get lucky ;-)
Do you want the patch I send to turn on the VFS_ENHANCEMENT #define in
lvm.c?
-chris
next prev parent reply other threads:[~2001-02-21 15:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-20 22:49 [linux-lvm] *** ANNOUNCEMENT *** LVM 0.9.1 beta5 available at www.sistina.com Heinz J. Mauelshagen
2001-02-21 4:19 ` [linux-lvm] snapshot of Reiserfs lvm, lvm
2001-02-21 8:59 ` Patrick Caulfield
2001-02-21 14:04 ` lvm
2001-02-21 14:11 ` Patrick Caulfield
2001-02-21 15:34 ` Chris Mason [this message]
2001-02-21 16:05 ` lvm
2001-02-21 16:12 ` Patrick Caulfield
2001-02-21 16:44 ` Andreas Dilger
2001-02-21 17:07 ` Chris Mason
2001-02-21 18:55 ` Andreas Dilger
2001-02-21 19:17 ` Chris Mason
2001-02-21 23:23 ` Andreas Dilger
2001-02-22 17:12 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2003-05-20 6:31 [linux-lvm] Snapshot of ReiserFS Dietmar Stein
2001-02-19 16:11 [linux-lvm] snapshot of Reiserfs lvm
2001-02-19 16:12 ` Joe Thornber
2001-02-19 17:04 ` Christoph Hellwig
2001-02-19 16:59 ` Joe Thornber
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=2090960000.982769673@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).