Markus Armbruster d8e39b7062 Use #include "..." for our own headers, <...> for others ... System headers should be included with <...>, our own headers with "...". Offenders tracked down with an ugly, brittle and probably buggy Perl script. Previous iteration was commit a9c94277f0. Delete inclusions of "string.h" and "strings.h" instead of fixing them to <string.h> and <strings.h>, because we always include these via osdep.h. Put the cleaned up system header includes first. While there, separate #include from file comment with exactly one blank line. Reviewed-by: Eric Blake <eblake@redhat.com> Reviewed-by: Thomas Huth <thuth@redhat.com> Signed-off-by: Markus Armbruster <armbru@redhat.com> Message-Id: <20180201111846.21846-2-armbru@redhat.com>		2018-02-09 05:05:11 +01:00
..
ivshmem-client	Clean up ill-advised or unusual header guards	2016-07-12 16:20:46 +02:00
ivshmem-server	Clean up ill-advised or unusual header guards	2016-07-12 16:20:46 +02:00
libvhost-user	contrib/libvhost-user: enable virtio config space messages	2018-01-18 21:52:37 +02:00
systemd	contrib: add systemd unit files	2017-12-20 22:29:26 +01:00
vhost-user-blk	contrib/vhost-user-blk: introduce a vhost-user-blk sample application	2018-01-18 21:52:37 +02:00
vhost-user-scsi	Use #include "..." for our own headers, <...> for others	2018-02-09 05:05:11 +01:00