From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [7121] fix a typo introduced in r7118
Date: Wed, 15 Apr 2009 19:48:17 +0000 [thread overview]
Message-ID: <E1LuB5l-00080J-H7@cvs.savannah.gnu.org> (raw)
Revision: 7121
http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=7121
Author: aurel32
Date: 2009-04-15 19:48:17 +0000 (Wed, 15 Apr 2009)
Log Message:
-----------
fix a typo introduced in r7118
Reported by Stefan Weil
Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
Modified Paths:
--------------
trunk/configure
Modified: trunk/configure
===================================================================
--- trunk/configure 2009-04-15 17:12:01 UTC (rev 7120)
+++ trunk/configure 2009-04-15 19:48:17 UTC (rev 7121)
@@ -1181,7 +1181,7 @@
fi
fi
-# Check for initofy functions when we are building linux-user
+# Check for inotify functions when we are building linux-user
# emulator. This is done because older glibc versions don't
# have syscall stubs for these implemented. In that case we
# don't provide them even if kernel supports them.
reply other threads:[~2009-04-15 19:48 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=E1LuB5l-00080J-H7@cvs.savannah.gnu.org \
--to=aurelien@aurel32.net \
--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).