From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LfhnM-0000L9-S7 for qemu-devel@nongnu.org; Fri, 06 Mar 2009 16:41:28 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LfhnM-0000Ko-AT for qemu-devel@nongnu.org; Fri, 06 Mar 2009 16:41:28 -0500 Received: from [199.232.76.173] (port=42167 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LfhnM-0000Kl-6w for qemu-devel@nongnu.org; Fri, 06 Mar 2009 16:41:28 -0500 Received: from moutng.kundenserver.de ([212.227.126.188]:60580) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LfhnL-0000ej-Kj for qemu-devel@nongnu.org; Fri, 06 Mar 2009 16:41:28 -0500 Received: from localhost ([127.0.0.1] ident=stefan) by flocke.weilnetz.de with esmtp (Exim 4.69) (envelope-from ) id 1LfhnK-0004zU-0x for qemu-devel@nongnu.org; Fri, 06 Mar 2009 22:41:26 +0100 Message-ID: <49B19885.1050306@mail.berlios.de> Date: Fri, 06 Mar 2009 22:41:25 +0100 From: Stefan Weil MIME-Version: 1.0 Subject: [Qemu-devel] [PATCH] Fix syntax error in Qemu documentation Content-Type: multipart/mixed; boundary="------------020101000703090300020908" Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: QEMU Developers This is a multi-part message in MIME format. --------------020101000703090300020908 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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 --------------020101000703090300020908 Content-Type: text/x-diff; name="qemu-doc.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="qemu-doc.patch" Fix texinfo syntax errors. Signed-off-by: Stefan Weil 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 [] 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 [] 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. --------------020101000703090300020908--