qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel][PATCH] Fix hxtool.
Date: Wed, 01 Jul 2009 19:13:35 +0200	[thread overview]
Message-ID: <4A4B993F.8090900@mail.berlios.de> (raw)
In-Reply-To: <1245499950-13035-1-git-send-email-weil@mail.berlios.de>

Stefan Weil schrieb:
> When converting from hx to texi format, hxtool (or to be
> more precise sh which interprets hxtool) used standard
> shell expansion of wildcards while writing lines to the
> output.
>
> Thus, something like "Password: ********"
> looked very different in the generated documentation.
>
> The patch disables this unwanted wildcard expansion.
>
> Signed-off-by: Stefan Weil <weil@mail.berlios.de>
> ---
>  hxtool |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hxtool b/hxtool
> index 885abe2..0fdbc64 100644
> --- a/hxtool
> +++ b/hxtool
> @@ -26,10 +26,10 @@ hxtotexi()
>              STEXI*|ETEXI*) flag=$(($flag^1))
>              ;;
>              DEFHEADING*)
> -            echo $(expr "$str" : "DEFHEADING(\(.*\))")
> +            echo "$(expr "$str" : "DEFHEADING(\(.*\))")"
>              ;;
>              *)
> -            test $flag -eq 1 && echo $str
> +            test $flag -eq 1 && echo "$str"
>              ;;
>          esac
>      done
>   

The patch is still missing in qemu.git. Without it, the next
version of http://www.nongnu.org/qemu/qemu-doc.html
will look bad. ;-)

Regards,

Stefan Weil

  reply	other threads:[~2009-07-01 17:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-20 12:12 [Qemu-devel] [PATCH] Fix hxtool Stefan Weil
2009-07-01 17:13 ` Stefan Weil [this message]
     [not found] <4A4BA43D.6040303@us.ibm.com>
2009-07-01 21:13 ` Stefan Weil

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A4B993F.8090900@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=aliguori@us.ibm.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).