scripts: add execute permission to several files

Most, but not all, files in scripts have execute permission. While we
don't need this in order to launch them via meson/ninja build rules,
it is nice to direct execution if they have execution permission. This
makes the practice consistent across all scripts.

Reviewed-by: Pavel Hrdina <phrdina@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

diff --git a/scripts/check-drivername.py b/scripts/check-drivername.py
old mode 100644 (file)
new mode 100755 (executable)

diff --git a/scripts/check-remote-protocol.py b/scripts/check-remote-protocol.py
old mode 100644 (file)
new mode 100755 (executable)

diff --git a/scripts/header-ifdef.py b/scripts/header-ifdef.py
old mode 100644 (file)
new mode 100755 (executable)

diff --git a/scripts/meson-install-dirs.py b/scripts/meson-install-dirs.py
old mode 100644 (file)
new mode 100755 (executable)

diff --git a/scripts/meson-install-symlink.py b/scripts/meson-install-symlink.py
old mode 100644 (file)
new mode 100755 (executable)

diff --git a/scripts/mock-noinline.py b/scripts/mock-noinline.py
old mode 100644 (file)
new mode 100755 (executable)

diff --git a/scripts/prohibit-duplicate-header.py b/scripts/prohibit-duplicate-header.py
old mode 100644 (file)
new mode 100755 (executable)