From: Jonathan Nieder <jrnieder@gmail•com>
To: git@vger•kernel.org
Cc: Ramsay Jones <ramsay@ramsay1•demon.co.uk>,
Clemens Buchacher <drizzd@aon•at>,
Marc Branchaud <marcnarc@xiplink•com>
Subject: [PATCH 1/9] mark Windows build scripts executable
Date: Mon, 25 Nov 2013 12:52:44 -0800 [thread overview]
Message-ID: <20131125205244.GR4212@google.com> (raw)
In-Reply-To: <20131125205119.GQ4212@google.com>
On Windows the convention is to rely on filename extensions to decide
whether a file is executable so Windows users are probably not relying
on the executable bit of these scripts, but on other platforms it can
be useful documentation.
Signed-off-by: Jonathan Nieder <jrnieder@gmail•com>
---
compat/vcbuild/scripts/clink.pl | 0
compat/vcbuild/scripts/lib.pl | 0
contrib/buildsystems/engine.pl | 0
contrib/buildsystems/generate | 0
contrib/buildsystems/parse.pl | 0
5 files changed, 0 insertions(+), 0 deletions(-)
mode change 100644 => 100755 compat/vcbuild/scripts/clink.pl
mode change 100644 => 100755 compat/vcbuild/scripts/lib.pl
mode change 100644 => 100755 contrib/buildsystems/engine.pl
mode change 100644 => 100755 contrib/buildsystems/generate
mode change 100644 => 100755 contrib/buildsystems/parse.pl
diff --git a/compat/vcbuild/scripts/clink.pl b/compat/vcbuild/scripts/clink.pl
old mode 100644
new mode 100755
diff --git a/compat/vcbuild/scripts/lib.pl b/compat/vcbuild/scripts/lib.pl
old mode 100644
new mode 100755
diff --git a/contrib/buildsystems/engine.pl b/contrib/buildsystems/engine.pl
old mode 100644
new mode 100755
diff --git a/contrib/buildsystems/generate b/contrib/buildsystems/generate
old mode 100644
new mode 100755
diff --git a/contrib/buildsystems/parse.pl b/contrib/buildsystems/parse.pl
old mode 100644
new mode 100755
--
1.8.4.1
next prev parent reply other threads:[~2013-11-25 21:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 20:51 [PATCH 0/9] War on #! lines in shell libraries Jonathan Nieder
2013-11-25 20:52 ` Jonathan Nieder [this message]
2013-11-25 20:53 ` [PATCH 2/9] mark perl test scripts executable Jonathan Nieder
2013-11-25 20:55 ` [PATCH 3/9] mark contributed hooks executable Jonathan Nieder
2013-11-25 20:58 ` [PATCH 4/9] contrib: remove git-p4import Jonathan Nieder
2013-11-26 12:31 ` Pete Wyckoff
2013-11-25 21:00 ` [PATCH 5/9 gitk] gitk: chmod +x po2msg Jonathan Nieder
2013-11-25 21:01 ` [PATCH 6/9 git-gui] git-gui: chmod +x po2msg, windows/git-gui.sh Jonathan Nieder
2013-11-25 21:02 ` [PATCH 7/9] test: make FILEMODE a lazy prereq Jonathan Nieder
2013-11-25 21:03 ` [PATCH 8/9] test: replace shebangs with descriptions in shell libraries Jonathan Nieder
2013-11-26 5:18 ` Eric Sunshine
2013-11-26 21:39 ` [PATCH 8/9 v2] " Jonathan Nieder
2013-11-25 21:03 ` [PATCH 9/9] remove #!interpreter line from " Jonathan Nieder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131125205244.GR4212@google.com \
--to=jrnieder@gmail$(echo .)com \
--cc=drizzd@aon$(echo .)at \
--cc=git@vger$(echo .)kernel.org \
--cc=marcnarc@xiplink$(echo .)com \
--cc=ramsay@ramsay1$(echo .)demon.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox