[Pkg-libvirt-commits] [libguestfs] 17/54: FAQ: Remove obsolete entry about libguestfs <= 1.13 and slow writes.

[Hilko Bengen]

This is an automated email from the git hooks/post-receive script.

bengen pushed a commit to branch debian
in repository libguestfs.

commit a18299e519f13263e1ad1e91019f50cdabe273ca
Author: Richard W.M. Jones <rjones at redhat.com>
Date:   Sun Feb 16 19:20:40 2014 +0000

    FAQ: Remove obsolete entry about libguestfs <= 1.13 and slow writes.
    
    Long since not a problem.
    
    (cherry picked from commit b987be513a919e91b79a045095f9b84db625165f)
---
 examples/guestfs-faq.pod | 12 ------------
 1 file changed, 12 deletions(-)

diff --git a/examples/guestfs-faq.pod b/examples/guestfs-faq.pod
index f88c810..85564a1 100644
--- a/examples/guestfs-faq.pod
+++ b/examples/guestfs-faq.pod
@@ -628,18 +628,6 @@ L<guestfs-performance(1)>.
 
 =head2 Upload or write seem very slow.
 
-In libguestfs E<lt> 1.13.16, the mount command
-(L<guestfs(3)/guestfs_mount>) enabled option C<-o sync> implicitly.
-This causes very poor write performance, and was one of the main
-gotchas for new libguestfs users.
-
-For libguestfs E<lt> 1.13.16, replace mount with C<mount-options>,
-leaving the first parameter as an empty string.
-
-You can also do this with more recent versions of libguestfs, but if
-you know that you are using libguestfs ≥ 1.13.16 then it's safe to use
-plain mount.
-
 If the underlying disk is not fully allocated (eg. sparse raw or
 qcow2) then writes can be slow because the host operating system has
 to do costly disk allocations while you are writing. The solution is

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-libvirt/libguestfs.git