From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dave Wysochanski <dwysocha@redhat.com>
Date: Wed, 07 Oct 2009 16:03:07 -0400
Subject: [PATCH, v2] unknown segment types
In-Reply-To: <87pr99ersa.fsf@twilight.int.mornfall.net.>
References: <87ljmzcz28.fsf@twilight.int.mornfall.net.>
	<4A56288F.4080604@redhat.com>
	<87k52h8wep.fsf@twilight.int.mornfall.net.>
	<4A564EEA.10607@redhat.com>
	<87vdlmhze5.fsf_-_@twilight.int.mornfall.net.>
	<87pr99ersa.fsf@twilight.int.mornfall.net.>
Message-ID: <1254945787.2499.8.camel@f10-node1>
List-Id: <lvm-devel.redhat.com>
To: lvm-devel@redhat.com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

On Tue, 2009-09-29 at 16:42 +0200, Petr Rockai wrote:
> Petr Rockai <prockai@redhat.com> writes:
> > here comes an amended patch for unknown segment types. This time, it won't let
> > people tinker with volume groups with unknown segtypes in it, but comes with
> > provisions to let tools override this safeguard when reasonable.
> a rebase of this same patch for current mainline (checked that it still works,
> too) is attached.
> 

Can you say where this applied previously?  Git hash or CVS info?
I've tried a few combinations around 9/29 but nothing applies cleanly so
far.