virCommandDoAsyncIO: Drop misleading statement about main event loop

Back in v1.0.3-rc1~235 when I was adding virCommandDoAsyncIO(),
the main event loop was used to poll() on the pipe to the child
process. But this was promptly changed to a separate thread
handling I/O in v1.0.3-rc1~127. However, the corresponding
comment to virCommandDoAsyncIO() still documents the original
state.

Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
Reviewed-by: Jonathon Jongsma <jjongsma@redhat.com>

diff --git a/src/util/vircommand.c b/src/util/vircommand.c
index cdc74bc2fdd4df3cee60ca211551a5a1fa866f8b..4f60432c0ac197af04a25ab8c0b1792112933cf6 100644 (file)
--- a/src/util/vircommand.c
+++ b/src/util/vircommand.c
@@ -3078,8 +3078,6 @@ virCommandFree(virCommand *cmd)
  *
  *      ...
  *
- *
- * The libvirt's event loop is used for handling stdios of @cmd.
  * Since current implementation uses strlen to determine length
  * of data to be written to @cmd's stdin, don't pass any binary
  * data. If you want to re-run command, you need to call this and