From: Stefan Weil <weil@mail.berlios.de>
To: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PATCH] configure: Fix spelling in comment and rework the comment
Date: Mon, 16 Nov 2009 19:59:18 +0100 [thread overview]
Message-ID: <1258397958-6668-1-git-send-email-weil@mail.berlios.de> (raw)
* Replace vill -> will.
* Comment was formatted to make it more readable
and to conform to the coding standard, too.
* Description of foo="" was completed.
Signed-off-by: Stefan Weil <weil@mail.berlios.de>
---
configure | 18 ++++++++++--------
1 files changed, 10 insertions(+), 8 deletions(-)
diff --git a/configure b/configure
index 4e19ab1..4e57206 100755
--- a/configure
+++ b/configure
@@ -174,15 +174,17 @@ case "$cpu" in
;;
esac
-# Default value for a variable defining feature "foo"
-# * foo="no", feature will only be used if --enable-foo arg is given
-# * foo="", feature will be searched for, and if found, will be used
-# * foo="yes", this value vill only be set by --enable-foo flag.
-# feature will searched for, if not found, configure exits with error
+# Default value for a variable defining feature "foo".
+# * foo="no" feature will only be used if --enable-foo arg is given
+# * foo="" feature will be searched for, and if found, will be used
+# unless --disable-foo is given
+# * foo="yes" this value will only be set by --enable-foo flag.
+# feature will searched for,
+# if not found, configure exits with error
#
-# Always add --enable-foo and --disable-foo command line args. Distributions want
-# to ensure that several features are compiled in, and it is impossible without a
-# --enable-foo that exits if feature is not found
+# Always add --enable-foo and --disable-foo command line args.
+# Distributions want to ensure that several features are compiled in, and it
+# is impossible without a --enable-foo that exits if a feature is not found.
bluez=""
brlapi=""
--
1.5.6.5
reply other threads:[~2009-11-16 18:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1258397958-6668-1-git-send-email-weil@mail.berlios.de \
--to=weil@mail.berlios.de \
--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).