From: Chris Mason <mason@suse.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Anyone brave tried lvm-1.0.3 & 2.4.18/2.4.19pre1 yet?
Date: Tue Feb 26 10:30:02 2002 [thread overview]
Message-ID: <2380410000.1014740958@tiny> (raw)
In-Reply-To: <20020226172201.A14976@sistina.com>
On Tuesday, February 26, 2002 05:22:01 PM +0100 "Heinz J . Mauelshagen" <mauelshagen@sistina.com> wrote:
> On Tue, Feb 26, 2002 at 09:12:13AM -0700, Andreas Dilger wrote:
>> On Feb 26, 2002 11:48 +0100, Heinz J . Mauelshagen wrote:
>> > Trying it right now ;-)
>>
>> Any thoughts on submitting updated LVM patches to Marcelo and/or Alan?
>> I believe Marcelo is much more accomodating with accepting patches, as
>> long as large patches are submitted for early -preX kernels.
>
> Yes, as mentioned in my other answer: have send him one.
I sent along the VFS locking patch as well. It was too late in the
pre series for 2.4.18, so I resent for 2.4.19.
-chris
next prev parent reply other threads:[~2002-02-26 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 22:37 [linux-lvm] Anyone brave tried lvm-1.0.3 & 2.4.18/2.4.19pre1 yet? Monte Milanuk
2002-02-26 4:48 ` Heinz J . Mauelshagen
2002-02-26 10:12 ` Andreas Dilger
2002-02-26 10:22 ` Heinz J . Mauelshagen
2002-02-26 10:30 ` Chris Mason [this message]
2002-02-27 3:31 ` Heinz J . Mauelshagen
2002-02-26 7:00 ` Urs Thuermann
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=2380410000.1014740958@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