Blob Blame History Raw
From 98f1746640771f2382c3e0d2b78ceb535a8d2cd0 Mon Sep 17 00:00:00 2001
From: "Richard W.M. Jones" <rjones@redhat.com>
Date: Wed, 17 Aug 2016 14:36:44 +0100
Subject: [PATCH] v2v: OVMF is now fully open source, fix the man page.

(cherry picked from commit 5c03a2ca8b0bcc5ea31a0c169dd022cad30d2ace)
---
 v2v/virt-v2v.pod | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod
index 434f57e..3e24025 100644
--- a/v2v/virt-v2v.pod
+++ b/v2v/virt-v2v.pod
@@ -768,8 +768,8 @@ VMware allows you to present UEFI firmware to guests (instead of the
 ordinary PC BIOS).  Virt-v2v can convert these guests, but requires
 that UEFI is supported by the target hypervisor.
 
-Currently KVM supports OVMF, a partially open source UEFI firmware,
-and can run these guests.
+Currently KVM supports OVMF, an open source UEFI firmware, and can run
+these guests.
 
 Since OVMF support was only recently added to KVM (in 2014/2015), not
 all target environments support UEFI guests yet:
-- 
1.8.3.1