[Qemu-devel] [PATCH] Fix syntax error in Qemu documentation

[Stefan Weil <weil@mail.berlios.de>]

[-- Attachment #1: Type: text/plain, Size: 276 bytes --]

The patch fixes this error message:

texi2html -monolithic -number trunk/qemu-doc.texi
** Unknown command `@EXAMPLE.COM' (left as is) (l. 641)
** Unknown command `@EXAMPLE.COM' (left as is) (l. 1426)
** Unknown command `@EXAMPLE.COM' (left as is) (l. 1433)

Regards
Stefan




[-- Attachment #2: qemu-doc.patch --]
[-- Type: text/x-diff, Size: 1949 bytes --]

Fix texinfo syntax errors.

Signed-off-by: Stefan Weil <weil@mail.berlios.de>

Index: trunk/qemu-doc.texi
===================================================================
--- trunk.orig/qemu-doc.texi	2009-03-06 22:32:00.000000000 +0100
+++ trunk/qemu-doc.texi	2009-03-06 22:32:05.000000000 +0100
@@ -638,7 +638,7 @@
 certificate's distinguished name. This is something that looks like
 @code{C=GB,O=ACME,L=Boston,CN=bob}. For SASL party, the ACL check is
 made against the username, which depending on the SASL plugin, may
-include a realm component, eg @code{bob} or @code{bob\@EXAMPLE.COM}.
+include a realm component, eg @code{bob} or @code{bob@@EXAMPLE.COM}.
 When the @option{acl} flag is set, the initial access list will be
 empty, with a @code{deny} policy. Thus no one will be allowed to
 use the VNC server until the ACLs have been loaded. This can be
@@ -1423,14 +1423,14 @@
 @item acl allow <aclname> <match> [<index>]
 add a match to the access control list, allowing access. The match will
 normally be an exact username or x509 distinguished name, but can
-optionally include wildcard globs. eg @code{*\@EXAMPLE.COM} to allow
+optionally include wildcard globs. eg @code{*@@EXAMPLE.COM} to allow
 all users in the @code{EXAMPLE.COM} kerberos realm. The match will
 normally be appended to the end of the ACL, but can be inserted
 earlier in the list if the optional @code{index} parameter is supplied.
 @item acl deny <aclname> <match> [<index>]
 add a match to the access control list, denying access. The match will
 normally be an exact username or x509 distinguished name, but can
-optionally include wildcard globs. eg @code{*\@EXAMPLE.COM} to allow
+optionally include wildcard globs. eg @code{*@@EXAMPLE.COM} to allow
 all users in the @code{EXAMPLE.COM} kerberos realm. The match will
 normally be appended to the end of the ACL, but can be inserted
 earlier in the list if the optional @code{index} parameter is supplied.