Blame snapper-remove-ext4-info-xml.patch

60a9bf2
--- a/doc/snapper.xml.in	2013-07-12 10:47:19.000000000 +0200
60a9bf2
+++ b/doc/snapper.xml.in	2013-07-29 12:43:31.582526830 +0200
60a9bf2
@@ -39,9 +39,7 @@
60a9bf2
 
60a9bf2
     <para>Snapper never modifies the content of snapshots. Thus snapper creates
60a9bf2
     read-only snapshots if supported by the kernel. Supported filesystems are
60a9bf2
-    btrfs and ext4 as well as snapshots of LVM logical volumes with
60a9bf2
-    thin-provisioning. Some filesystems might not be supported depending on your
60a9bf2
-    installation.</para>
60a9bf2
+    btrfs as well as snapshots of LVM logical volumes with thin-provisioning.</para>
60a9bf2
   </refsect1>
60a9bf2
 
60a9bf2
   <refsect1 id='concepts'>
60a9bf2
@@ -235,7 +233,7 @@
60a9bf2
 	    <varlistentry>
60a9bf2
 	      <term><option>-f, --fstype</option> <replaceable>fstype</replaceable></term>
60a9bf2
 	      <listitem>
60a9bf2
-		<para>Manually set filesystem type. Supported values are btrfs, ext4 and lvm. For
60a9bf2
+		<para>Manually set filesystem type. Supported values are btrfs and lvm. For
60a9bf2
 		lvm, snapper uses LVM thin-provisioned snapshots. The filesystem type on top of
60a9bf2
 		LVM must be provided in parentheses, e.g. lvm(xfs).</para>
60a9bf2
 		<para>Without this option snapper tries to detect the filesystem.</para>