git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Rada <marada@uwaterloo.ca>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCH] tests: make all test files executable
Date: Thu, 01 Oct 2009 21:59:20 -0400	[thread overview]
Message-ID: <4AC55E78.7010109@mailservices.uwaterloo.ca> (raw)

For consistency with the rest of the test files.

Signed-off-by: Mark Rada <marada@uwaterloo.ca>
---

On 2009-10-01, at 4:13 AM, Jakub Narebski wrote:
>> diff --git a/t/t9501-gitweb-standalone-http-status.sh b/t/t9501-gitweb-standalone-http-status.sh
>> index d0ff21d..0688a57 100644
>> --- a/t/t9501-gitweb-standalone-http-status.sh
>> +++ b/t/t9501-gitweb-standalone-http-status.sh
> 
> BTW. the rest of test scripts are executable, but not this one? Why?
> (But correcting this should be done, if needed, in separate commit).

I noticed one other test script that was not set to be executable.


 0 files changed, 0 insertions(+), 0 deletions(-)
 mode change 100644 => 100755 t/t5531-deep-submodule-push.sh
 mode change 100644 => 100755 t/t9501-gitweb-standalone-http-status.sh

diff --git a/t/t5531-deep-submodule-push.sh b/t/t5531-deep-submodule-push.sh
old mode 100644
new mode 100755
diff --git a/t/t9501-gitweb-standalone-http-status.sh
b/t/t9501-gitweb-standalone-http-status.sh
old mode 100644
new mode 100755
-- 
1.6.5.rc2

             reply	other threads:[~2009-10-02  2:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02  1:59 Mark Rada [this message]
2009-10-02  8:01 ` [PATCH] tests: make all test files executable Jeff King
2009-10-02  8:39   ` Jeff King
2009-10-04 13:18     ` Mark Rada
2009-10-04 13:40       ` Jeff King
2009-10-05  1:25         ` Mark Rada
2009-10-05  9:59           ` Jeff King
  -- strict thread matches above, loose matches on Subject: below --
2009-10-06  1:46 Mark Rada
2009-10-06 10:00 ` Jeff King

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=4AC55E78.7010109@mailservices.uwaterloo.ca \
    --to=marada@uwaterloo.ca \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).