From: Joe Thornber <thornber@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] LVM2-Snapshot
Date: Thu Mar 11 07:06:00 2004 [thread overview]
Message-ID: <20040311120958.GH18345@reti> (raw)
In-Reply-To: <OF36A82CA1.D42E4925-ON80256E54.003D7822-80256E54.003DD0DD@philips.com>
On Thu, Mar 11, 2004 at 11:13:12AM +0000, darren.miller@philips.com wrote:
> Tried to apply the udm patch selection to vanilla 2.6.4 kernel recieved a
> shed load of failures and the kernel refused to build. I am not a
> programmer so I have no clue how to rectify these issues. do you have
> anything that works?
The last udm was 2.6.4-rc2-udm1, I'm working on a 2.6.4 version now.
^^^
- Joe
next prev parent reply other threads:[~2004-03-11 12:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 6:13 [linux-lvm] LVM2-Snapshot darren.miller
2004-03-11 7:06 ` Joe Thornber [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-30 12:09 darren.miller
2004-03-11 8:24 darren.miller
2004-03-11 8:06 darren.miller
2004-03-10 11:41 darren.miller
2004-03-10 11:28 Christoph Pleger
2004-03-11 4:16 ` Joe Thornber
2004-03-11 7:23 ` Craig Ringer
2004-03-11 8:34 ` Alasdair G Kergon
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=20040311120958.GH18345@reti \
--to=thornber@redhat.com \
--cc=linux-lvm@redhat.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