Hi, Thankyou for the fix - libvirt now requires Signed-off-by in every commit in accordance with this https://developercertificate.org/ Could you read that and either re-send the patch with the SoB added to the commit message, or simply reply to this mail with it and i'll add when pushing. On Thu, May 03, 2018 at 12:17:19PM +0200, Ville Skyttä wrote: > --- > docs/aclpolkit.html.in | 2 +- > docs/api.html.in | 2 +- > docs/contribute.html.in | 2 +- > docs/downloads.html.in | 2 +- > docs/drvbhyve.html.in | 2 +- > docs/drvesx.html.in | 2 +- > docs/drvlxc.html.in | 2 +- > docs/errors.html.in | 2 +- > docs/firewall.html.in | 2 +- > docs/formatdomain.html.in | 12 ++++++------ > docs/formatdomaincaps.html.in | 2 +- > docs/internals/rpc.html.in | 2 +- > docs/locking-sanlock.html.in | 2 +- > docs/news.xml | 2 +- > docs/storage.html.in | 2 +- > docs/support.html.in | 2 +- > 16 files changed, 21 insertions(+), 21 deletions(-) > > diff --git a/docs/aclpolkit.html.in b/docs/aclpolkit.html.in > index 0e3c8e9..98d06da 100644 > --- a/docs/aclpolkit.html.in > +++ b/docs/aclpolkit.html.in > @@ -396,7 +396,7 @@ polkit.addRule(function(action, subject) { > To achieve this we need to write a rule which checks > whether the <code>connect_driver</code> attribute > is <code>LXC</code> and the <code>domain_name</code> > - attribute is <code>demo</code>, and match on a action > + attribute is <code>demo</code>, and match on action > name of <code>org.libvirt.api.domain.getattr</code>. Using > the javascript rules format, this ends up written as > </p> > diff --git a/docs/api.html.in b/docs/api.html.in > index 27abed6..288b9ec 100644 > --- a/docs/api.html.in > +++ b/docs/api.html.in > @@ -155,7 +155,7 @@ > </ul> > </li> > <li><b>Enumeration</b> [virConnectList..., virConnectNumOf...] > - <p>Used to enumerate a set of object available to an given > + <p>Used to enumerate a set of object available to a given > hypervisor connection such as:</p> > <ul> > <li> > diff --git a/docs/contribute.html.in b/docs/contribute.html.in > index 158c91c..42a1b2f 100644 > --- a/docs/contribute.html.in > +++ b/docs/contribute.html.in > @@ -80,7 +80,7 @@ > and future growth of the project, that there are a people > who evangalise the work created by the project. This can > take many forms, writing blog posts (about usage of features, > - personal user experiances, areas for future work, and more), > + personal user experiences, areas for future work, and more), > syndicating docs and blogs via social media, giving user > group and/or conference talks about libvirt.</li> > <li><strong>User assistance</strong>. Since documentation > diff --git a/docs/downloads.html.in b/docs/downloads.html.in > index 8cca203..2956a4f 100644 > --- a/docs/downloads.html.in > +++ b/docs/downloads.html.in > @@ -457,7 +457,7 @@ > (first release in the middle of Jan, then skip the Feb release), giving > a total of 11 releases a year. The Python and Perl modules will aim to > release at the same time as the core libvirt module. Other modules have > - independant ad-hoc releases with no fixed time schedle. > + independent ad-hoc releases with no fixed time schedule. > </p> > > <h2><a id="numbering">Release numbering</a></h2> > diff --git a/docs/drvbhyve.html.in b/docs/drvbhyve.html.in > index 63260af..bde8298 100644 > --- a/docs/drvbhyve.html.in > +++ b/docs/drvbhyve.html.in > @@ -239,7 +239,7 @@ to let a guest boot or start a guest using:</p> > > <pre>start --console domname</pre> > > -<p><b>NB:</b> An bootloader configured to require user interaction will prevent > +<p><b>NB:</b> A bootloader configured to require user interaction will prevent > the domain from starting (and thus <code>virsh console</code> or <code>start > --console</code> from functioning) until the user interacts with it manually on > the VM host. Because users typically do not have access to the VM host, > diff --git a/docs/drvesx.html.in b/docs/drvesx.html.in > index 417aca4..901d659 100644 > --- a/docs/drvesx.html.in > +++ b/docs/drvesx.html.in > @@ -437,7 +437,7 @@ ethernet0.checkMACAddress = "false" > <dl> > <dt><code>auto</code></dt> > <dd> > - This isn't a actual controller model. If specified the ESX driver > + This isn't an actual controller model. If specified the ESX driver > tries to detect the SCSI controller model referenced in the > <code>.vmdk</code> file and use it. Autodetection fails when a > SCSI controller has multiple disks attached and the SCSI controller > diff --git a/docs/drvlxc.html.in b/docs/drvlxc.html.in > index 44c4960..6ee9ee8 100644 > --- a/docs/drvlxc.html.in > +++ b/docs/drvlxc.html.in > @@ -429,7 +429,7 @@ be considered secure against exploits of the host OS. The sVirt SELinux > driver provides a way to secure containers even when the "user" namespace > is not used. The cost is that writing a policy to allow execution of > arbitrary OS is not practical. The SELinux sVirt policy is typically > -tailored to work with an simpler application confinement use case, > +tailored to work with a simpler application confinement use case, > as provided by the "libvirt-sandbox" project. > </p> > > diff --git a/docs/errors.html.in b/docs/errors.html.in > index 8f4f7d4..ea42728 100644 > --- a/docs/errors.html.in > +++ b/docs/errors.html.in > @@ -29,7 +29,7 @@ set specifically to a connection with</p> > call it with the error information</li><li>otherwise call <a href="html/libvirt-virterror.html#virDefaultErrorFunc">virDefaultErrorFunc</a> > which is the default error function of the library issuing the error > on stderr</li><li>save the error in the connection for later retrieval with <a href="html/libvirt-virterror.html#virConnGetLastError">virConnGetLastError</a></li></ol></li> > - <li>otherwise like when failing to create an hypervisor connection: > + <li>otherwise like when failing to create a hypervisor connection: > <ol><li>if there is a global callback set with <a href="html/libvirt-virterror.html#virSetErrorFunc">virSetErrorFunc</a>, > call it with the error information</li><li>otherwise call <a href="html/libvirt-virterror.html#virDefaultErrorFunc">virDefaultErrorFunc</a> > which is the default error function of the library issuing the error > diff --git a/docs/firewall.html.in b/docs/firewall.html.in > index 11c3c81..0a50687 100644 > --- a/docs/firewall.html.in > +++ b/docs/firewall.html.in > @@ -11,7 +11,7 @@ > <ul> > <li>The virtual network driver > <br /><br /> > - This provides a isolated bridge device (ie no physical NICs > + This provides an isolated bridge device (ie no physical NICs > enslaved). Guest TAP devices are attached to this bridge. > Guests can talk to each other and the host, and optionally the > wider world. > diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in > index 8e864f7..b65fea0 100644 > --- a/docs/formatdomain.html.in > +++ b/docs/formatdomain.html.in > @@ -622,7 +622,7 @@ > > <code>order</code> allows to specify the order to add the online vcpus. > For hypervisors/platforms that require to insert multiple vcpus at once > - the order may be duplicated accross all vcpus that need to be > + the order may be duplicated across all vcpus that need to be > enabled at once. Specifying order is not necessary, vcpus are then > added in an arbitrary order. If order info is used, it must be used for > all online vcpus. Hypervisors may clear or update ordering information > @@ -4058,7 +4058,7 @@ > pcie-switch-upstream-port, and of course for this to work > properly, you will need to decrease the pcie-expander-bus' > busNr accordingly so that there are enough unused bus > - numbers above it to accomodate giving out one bus number for > + numbers above it to accommodate giving out one bus number for > the upstream-port and one for each downstream-port (in > addition to the pcie-root-port and the pcie-expander-bus > itself). > @@ -4212,7 +4212,7 @@ > <dd>This is the fully qualified path of the file associated > with the lockspace. The offset specifies where the lease > is stored within the file. If the lock manager does not > - require a offset, just pass 0. > + require an offset, just pass 0. > </dd> > </dl> > > @@ -4867,7 +4867,7 @@ > (<span class="since">Since 0.10.0</span>). For example, in order > to work properly with both an 802.1Qbh switch and an Open vSwitch > switch, you may choose to specify no type, but both > - an <code>profileid</code> (in case the switch is 802.1Qbh) and > + a <code>profileid</code> (in case the switch is 802.1Qbh) and > an <code>interfaceid</code> (in case the switch is Open vSwitch) > (you may also omit the other attributes, such as managerid, > typeid, or profileid, to be filled in from the > @@ -6174,7 +6174,7 @@ qemu-kvm -net nic,model=? /dev/null > set to an empty string, then VNC access is disabled. The > <code>keymap</code> attribute specifies the keymap to use. It is > possible to set a limit on the validity of the password by giving > - an timestamp <code>passwdValidTo='2010-04-09T15:51:00'</code> > + a timestamp <code>passwdValidTo='2010-04-09T15:51:00'</code> > assumed to be in UTC. The <code>connected</code> attribute allows > control of connected client during password changes. VNC accepts > <code>keep</code> value only <span class="since">since 0.9.3</span>. > @@ -6216,7 +6216,7 @@ qemu-kvm -net nic,model=? /dev/null > <code>passwd</code> attribute is set to an empty string, then > SPICE access is disabled. The <code>keymap</code> attribute > specifies the keymap to use. It is possible to set a limit on > - the validity of the password by giving an timestamp > + the validity of the password by giving a timestamp > <code>passwdValidTo='2010-04-09T15:51:00'</code> assumed to be > in UTC. > </p> > diff --git a/docs/formatdomaincaps.html.in b/docs/formatdomaincaps.html.in > index 6bfcaf6..027e115 100644 > --- a/docs/formatdomaincaps.html.in > +++ b/docs/formatdomaincaps.html.in > @@ -81,7 +81,7 @@ > > <h3><a id="elementsCPUAllocation">CPU Allocation</a></h3> > > - <p>Before any devices capability occurs, there might be a info on domain > + <p>Before any devices capability occurs, there might be info on domain > wide capabilities, e.g. virtual CPUs:</p> > > <pre> > diff --git a/docs/internals/rpc.html.in b/docs/internals/rpc.html.in > index fca9cb7..048192f 100644 > --- a/docs/internals/rpc.html.in > +++ b/docs/internals/rpc.html.in > @@ -133,7 +133,7 @@ > </dd> > <dt><code>serial</code></dt> > <dd> > - This is an number that starts from 1 and increases > + This is a number that starts from 1 and increases > each time a method call packet is sent. A reply or > stream packet will have a serial number matching the > original method call packet serial. Events always > diff --git a/docs/locking-sanlock.html.in b/docs/locking-sanlock.html.in > index 9b36561..3ee9849 100644 > --- a/docs/locking-sanlock.html.in > +++ b/docs/locking-sanlock.html.in > @@ -76,7 +76,7 @@ SANLOCKOPTS="-w 0" > configuration file for each libvirt driver that is using > sanlock. For QEMU, we will edit <code>/etc/libvirt/qemu-sanlock.conf</code> > There is one mandatory parameter that needs to be set, > - the <code>host_id</code>. This is a integer between > + the <code>host_id</code>. This is an integer between > 1 and 2000, which must be set to a <strong>unique</strong> > value on each host running virtual machines. > </p> > diff --git a/docs/news.xml b/docs/news.xml > index d67d5a7..8018141 100644 > --- a/docs/news.xml > +++ b/docs/news.xml > @@ -1206,7 +1206,7 @@ > <description> > The <code>vgaconf</code> attribute was added to <code>video</code>'s > <code>driver</code> element. Possible values are: <code>on</code>, > - <code>off</code>, and <code>io</code>. It controlls the way how > + <code>off</code>, and <code>io</code>. It controls the way how > bhyve exposes video devices to its guests; various guest OSes might > require different settings to boot properly. > </description> > diff --git a/docs/storage.html.in b/docs/storage.html.in > index 3f1aec1..1906aa6 100644 > --- a/docs/storage.html.in > +++ b/docs/storage.html.in > @@ -759,7 +759,7 @@ > This provides a pool based on Virtuozzo storage. Virtuozzo Storage is > a highly available distributed software-defined storage with built-in > replication and disaster recovery. More detailed information about > - Virtuozzo storage and its managment can be found here: > + Virtuozzo storage and its management can be found here: > > <a href="https://openvz.org/Virtuozzo_Storage";>Virtuozzo Storage</a>). > </p> > diff --git a/docs/support.html.in b/docs/support.html.in > index 1a9438f..38f2f90 100644 > --- a/docs/support.html.in > +++ b/docs/support.html.in > @@ -199,7 +199,7 @@ > return an error indicating it is not supported. Likewise libvirt will > make reasonable efforts to keep API calls working across hypervisor > releases even if the underlying implementation changes. In cases where > - this is impossible, an suitable error will be reported. The list of > + this is impossible, a suitable error will be reported. The list of > APIs which have implementations <a href="hvsupport.html">is detailed separately</a>. > </p> > > -- > 2.14.1 > > -- > libvir-list mailing list > libvir-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/libvir-list Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
