summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEric Blake <eblake@redhat.com>2013-04-19 14:18:14 -0600
committerEric Blake <eblake@redhat.com>2013-04-19 14:31:16 -0600
commitf2b1504a79736cdc17d68581434ca327303f2474 (patch)
treea8061ba6b110be155c532b93bd38ab4c8c0a7aee
parent919889aa59f93176e46b00956d2dc0693f1f05c1 (diff)
downloadlibvirt-python-split-f2b1504a79736cdc17d68581434ca327303f2474.zip
libvirt-python-split-f2b1504a79736cdc17d68581434ca327303f2474.tar.gz
libvirt-python-split-f2b1504a79736cdc17d68581434ca327303f2474.tar.xz
docs: fix usage of 'onto'v1.0.5-rc1v1.0.5
http://www.uhv.edu/ac/newsletters/writing/grammartip2009.07.01.htm (and several other sites) give hints that 'onto' is best used if you can also add 'up' just before it and still make sense. In many cases in the code base, we really want the two-word form, or even a simplification to just 'on' or 'to'. * docs/hacking.html.in: Use correct 'on to'. * python/libvirt-override.c: Likewise. * src/lxc/lxc_controller.c: Likewise. * src/util/virpci.c: Likewise. * daemon/THREADS.txt: Use simpler 'on'. * docs/formatdomain.html.in: Better usage. * docs/internals/rpc.html.in: Likewise. * src/conf/domain_event.c: Likewise. * src/rpc/virnetclient.c: Likewise. * tests/qemumonitortestutils.c: Likewise. * HACKING: Regenerate. Signed-off-by: Eric Blake <eblake@redhat.com>
-rw-r--r--libvirt-override.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/libvirt-override.c b/libvirt-override.c
index 3d8490c..244b7ec 100644
--- a/libvirt-override.c
+++ b/libvirt-override.c
@@ -4,7 +4,7 @@
* entry points where an automatically generated stub is
* unpractical
*
- * Copyright (C) 2005, 2007-2012 Red Hat, Inc.
+ * Copyright (C) 2005, 2007-2013 Red Hat, Inc.
*
* Daniel Veillard <veillard@redhat.com>
*/
@@ -5084,7 +5084,7 @@ libvirt_virEventRegisterImpl(ATTRIBUTE_UNUSED PyObject * self,
updateTimeoutName = py_str(updateTimeoutObj);
removeTimeoutName = py_str(removeTimeoutObj);
- /* Inc refs since we're holding onto these objects until
+ /* Inc refs since we're holding on to these objects until
* the next call (if any) to this function.
*/
Py_INCREF(addHandleObj);