Signed-off-by: NJiri Denemark <jdenemar@redhat.com>

Catch up with changes that have been pushed but didn't include
updates to the NEWS file themselves.

With the QEMU components in place, provide the XML parsing to
invoke that code when given the following XML snippet:

    <hostdev mode='subsystem' type='scsi_host'>
      <source protocol='vhost' wwpn='naa.501234567890abcd'/>
    </hostdev>

An optional address element can be specified within the hostdev
(pick CCW or PCI as necessary):

    <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0625'/>
    <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>

Add basic vhost-scsi tests which were cloned from hostdev-scsi-virtio-scsi
in both xml2argv and xml2xml. Added ones for both vhost-scsi-ccw and
vhost-scsi-pci since the syntaxes are slightly different between them.

Also adjusted the docs to describe the changes.
Signed-off-by: NEric Farman <farman@linux.vnet.ibm.com>
Reviewed-by: NBoris Fiuczynski <fiuczy@linux.vnet.ibm.com>

now that we have a new global vboxDriver object, remove the old
vboxGlobalData struct and all references to it.

Not closing the <li> tag on a separate line causes the plain
text version of the file to have no empty line between entries.

Commit v1.3.3-181-gb028e9d7 implmented support for
VIR_MIGRATE_PARAM_PERSIST_XML migration parameter, but forgot to update
virsh.

https://bugzilla.redhat.com/show_bug.cgi?id=835300Signed-off-by: NJiri Denemark <jdenemar@redhat.com>

New line character in name of storagepool is now forbidden because it
mess virsh output and can be confusing for users.
Validation of name is done in driver, after parsing XML to avoid
problems with dissappeared pools which was already created with
new-line char in name.
Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>

All of these changes have already been merged, so document
them properly.

The new format requires some tweaks to be translated into
a nice plain text output, and the XSLT stylesheet needs to
be updated to match.

We're going to change the format of the source HTML quite
a bit, and we're going to have to update the XSLT stylesheet
accordingly.

Move 2016 releases out of the way before doing so.

This entry is meant to both get the ball rolling on the
switch and to provide a blueprint of what NEWS file entries
are supposed to look like.

* docs/news.html.in: update for the release
* po/*.po*: regenerated

* docs/news.html.in: updated for release
* po/*.po*: regenerated

* docs/news.html.in: update for release
* po/*po*: regenerate

* docs/news.html.in: updated for release
* po/*.po*: regenerated

* docs/news.html.in: update documentation
* po/*.po*: regenerate

* docs/news.html.in: update with 1.3.5 data

* docs/news.html.in libvirt.spec.in: update for release
* po/*.po* : regenerated

- docs/news.html.in libvirt.spec.in: update for release
- po/*.po*: regenerated

* docs/news.html.in libvirt.spec.in: update for release
* po/*.po*: regenerated

It was only used in two instances, so get rid of it for
consistency's sake.

Now that the first release made in 2016 is out, we can move all
entries for 2015 to their own file, just like we did for all previous
years.

* docs/news.html.in libvirt.spec.in: update for release
* po/*.po*: regenerated

* docs/news.html.in libvirt.spec.in: update for release
* po/*.po*: regenerated

* docs/news.html.in libvirt.spec.in: Updated for the release
* po/*.po*: regenerated

Update cfg.mk to ignore the split files during
syntax-check (thanks Martin).

There were some inconsistencies, eg. the number of digits used for
the day. The month name was also spelled out instead of abbreviated
in some instances.

There were some inconsistencies; now the section title is always
one of Bug Fixes, Cleanups, Documentation, Features, Improvements,
Portability, Security.

Make sure there is always an empty line between sections.

Some of the paragraphs were not properly indented: while this was
not a problem in the HTML version, you could tell the difference
in the plain text version.

Some <br/> tags were missing from the end of the corresponding
line, some of there were in the middle of the line instead.

Mostly missing space between change description and author name or
spurious space before section title.

Reflow the introductory paragraph as well.

Sort all items into the standard categories: Features, Bug Fixes,
Improvements, Cleanups, etc.

The sorting is somewhat arbitrary in certain instances.

The changes for releases earlier than 0.7.1 were mostly lumped
together as opposed to being tidly organized with one change per
line, like we have done from that point onwards.

As a result, they look awful in the HTML version and don't work
too well in the plain text version either.

Luckily, except for the very first releases, the information is
still very detailed, so it's enough to organize it properly.

The changes for releases earlier than 0.7.1 were mostly lumped
together as opposed to being tidly organized with one change per
line, like we have done from that point onwards.

As a result, they look awful in the HTML version and don't work
too well in the plain text version either.

Luckily, except for the very first releases, the information is
still very detailed, so it's enough to organize it properly.

The changes for releases earlier than 0.7.1 were mostly lumped
together as opposed to being tidly organized with one change per
line, like we have done from that point onwards.

As a result, they look awful in the HTML version and don't work
too well in the plain text version either.

Luckily, except for the very first releases, the information is
still very detailed, so it's enough to organize it properly.