From: Sergio Durigan Junior <sergiodj@redhat.com>
To: GDB Patches <gdb-patches@sourceware.org>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>
Subject: [commit/obvious] Set executable bit on analyze-racy-logs.py
Date: Sun, 06 Mar 2016 22:34:00 -0000 [thread overview]
Message-ID: <1457303627-7146-1-git-send-email-sergiodj@redhat.com> (raw)
In-Reply-To: <87ziucv0qf.fsf@redhat.com>
I forgot to do it in my previous commit. This is necessary because we
execute the script directly on gdb/testsuite/Makefile.in.
gdb/testsuite/ChangeLog:
2016-03-06 Sergio Durigan Junior <sergiodj@redhat.com>
* analyze-racy-logs.py: Set executable bit.
---
gdb/testsuite/ChangeLog | 4 ++++
gdb/testsuite/analyze-racy-logs.py | 0
2 files changed, 4 insertions(+)
mode change 100644 => 100755 gdb/testsuite/analyze-racy-logs.py
diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index a96156d..668f9f0 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,7 @@
+2016-03-06 Sergio Durigan Junior <sergiodj@redhat.com>
+
+ * analyze-racy-logs.py: Set executable bit.
+
2016-03-05 Sergio Durigan Junior <sergiodj@redhat.com>
* Makefile.in (DEFAULT_RACY_ITER): New variable.
diff --git a/gdb/testsuite/analyze-racy-logs.py b/gdb/testsuite/analyze-racy-logs.py
old mode 100644
new mode 100755
--
2.4.3
prev parent reply other threads:[~2016-03-06 22:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r3gcgm91.fsf@redhat.com>
2016-02-25 17:01 ` [PATCH] Improve analysis of racy testcases Pedro Alves
2016-02-28 21:44 ` Sergio Durigan Junior
2016-03-01 11:56 ` Pedro Alves
2016-03-06 1:29 ` Sergio Durigan Junior
2016-02-25 18:34 ` Antoine Tremblay
2016-03-01 5:58 ` Sergio Durigan Junior
2016-03-14 12:32 ` Antoine Tremblay
2016-03-14 12:45 ` Pedro Alves
2016-03-14 14:04 ` Antoine Tremblay
2016-04-27 17:18 ` Antoine Tremblay
2016-03-01 5:51 ` [PATCH v2] " Sergio Durigan Junior
2016-03-01 12:41 ` Pedro Alves
2016-03-06 1:44 ` Sergio Durigan Junior
2016-03-06 22:34 ` Sergio Durigan Junior [this message]
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=1457303627-7146-1-git-send-email-sergiodj@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
/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