All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zac Slade <krakrjak@volumehost.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] pvresize patch pending
Date: Fri, 28 Oct 2005 12:17:54 -0500	[thread overview]
Message-ID: <1130519874.43625d4253324@webmail.volumehost.com> (raw)
In-Reply-To: <20051028170130.GH11086@agk.surrey.redhat.com>

Quoting Alasdair G Kergon <agk@redhat.com>:

> On Fri, Oct 28, 2005 at 11:59:56AM -0500, Zac Slade wrote:
> > Is this the right venue to distribute this patch 
> 
> Yes!

Well alright.  Attached is a unified diff I validated that it merges
successfully against LVM2.2.01.13.tar.gz and LVM2.2.01.14.tar.gz.  Those files I
obtained through gentoo's portage system.  I also checked out the cvs and the
patch does apply successfully.  To integrate the patch just enter the
distribution directory where the LVM2 sources are and execute, patch -p1 <
path-to.patch.

For testing we used an lv that was mounted on a loopback device.  The only
option that pvresize will take is a pv pathname.

Here's your patch!
Zac Slade
krakrjak@volumehost.com


-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/

  reply	other threads:[~2005-10-28 17:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-28 16:59 [linux-lvm] pvresize patch pending Zac Slade
2005-10-28 17:01 ` Alasdair G Kergon
2005-10-28 17:17   ` Zac Slade [this message]
2005-10-28 17:55     ` Zac Slade
2005-10-28 19:27       ` Alasdair G Kergon
2005-10-28 20:14         ` Zak Kipling
2005-10-28 21:21           ` Alasdair G Kergon
2005-10-29  0:37             ` Zac Slade
2005-10-29  1:02               ` Alasdair G Kergon
2005-10-29 20:08                 ` Alasdair G Kergon
2005-11-04  1:53                 ` Zac Slade
2005-10-31  2:42           ` 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=1130519874.43625d4253324@webmail.volumehost.com \
    --to=krakrjak@volumehost.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.