From: wim@unetix.nl
To: LVM mailing list <linux-lvm@sistina.com>
Subject: Re: [linux-lvm] How to create a device mapper patch?
Date: Mon Oct 27 08:32:02 2003 [thread overview]
Message-ID: <200310240936.30411.wim@unetix.nl> (raw)
In-Reply-To: <20031023190424.GB1497@DUK2.13thfloor.at>
On Thursday 23 October 2003 21:04, you wrote:
> On Thu, Oct 23, 2003 at 04:26:53PM +0200, wim@unetix.nl wrote:
> > for the kernel. The patches directory only contains patches
> > for 2.4.20 en 21 so, how do I generate a patch for 2.4.22?
> > Device mapper is version 1.00.05
>
> http://evms.sourceforge.net/install/kernel.html#dm-patches
>
> HTH,
> Herbert
>
Ye, thanks , the following link is allso good :
http://people.sistina.com/~thornber/patches/
Would be good to add this link in the README
or INSTALL files in the standard device-mapper
package for people searching for patches.
Thanks
Wim Bakker
This e-mail was scanned by RAV Antivirus!
next prev parent reply other threads:[~2003-10-27 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 9:28 [linux-lvm] How to create a device mapper patch? wim
2003-10-23 14:05 ` Herbert Poetzl
2003-10-27 8:32 ` wim [this message]
2003-10-23 16:10 ` Herbert Poetzl
2003-10-24 5:31 ` Heinz J . Mauelshagen
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=200310240936.30411.wim@unetix.nl \
--to=wim@unetix.nl \
--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