From: "Bob Feng" <bob.c.feng@intel.com>
To: Philippe Mathieu-Daude <philmd@redhat.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Gao, Liming" <liming.gao@intel.com>, Laszlo Ersek <lersek@redhat.com>
Subject: Re: [PATCH 1/3] BaseTools: Let the GetMaintainer.py script be executable
Date: Fri, 18 Oct 2019 01:44:06 +0000 [thread overview]
Message-ID: <08650203BA1BD64D8AD9B6D5D74A85D16154CB80@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20191016140940.18844-2-philmd@redhat.com>
Hi Phil,
To make python script to be executable, I think only change file permission would not be enough. There also need to be a shebang
#!/usr/bin/env python at the top of this script.
But from the patch 3/3, I see in the GitCcCmd.sh, GetMaintainer.py is called by "python ${EDK_TOOLS_PATH}/Scripts/GetMaintainer.py --quiet"
Python interpreter is called explicit, so I think it's not necessary to change GetMaintainer.py permission.
Thanks,
Bob
-----Original Message-----
From: Philippe Mathieu-Daude [mailto:philmd@redhat.com]
Sent: Wednesday, October 16, 2019 10:10 PM
To: Leif Lindholm <leif.lindholm@linaro.org>; devel@edk2.groups.io
Cc: Feng, Bob C <bob.c.feng@intel.com>; Gao, Liming <liming.gao@intel.com>; Laszlo Ersek <lersek@redhat.com>; Philippe Mathieu-Daude <philmd@redhat.com>
Subject: [PATCH 1/3] BaseTools: Let the GetMaintainer.py script be executable
The GetMaintainer.py script use the "if __name__ == '__main__'"
evaluation so it expects to be run as a standalone program.
We have other Python scripts with the executable permission, let this one be executable too.
Signed-off-by: Philippe Mathieu-Daude <philmd@redhat.com>
---
BaseTools/Scripts/GetMaintainer.py | 0
1 file changed, 0 insertions(+), 0 deletions(-) mode change 100644 => 100755 BaseTools/Scripts/GetMaintainer.py
diff --git a/BaseTools/Scripts/GetMaintainer.py b/BaseTools/Scripts/GetMaintainer.py
old mode 100644
new mode 100755
--
2.21.0
next prev parent reply other threads:[~2019-10-18 1:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 14:09 [PATCH 0/3] BaseTools: Add a script to use with 'git-send-email --cc-cmd' Philippe Mathieu-Daudé
2019-10-16 14:09 ` [PATCH 1/3] BaseTools: Let the GetMaintainer.py script be executable Philippe Mathieu-Daudé
2019-10-18 1:44 ` Bob Feng [this message]
2019-10-16 14:09 ` [PATCH 2/3] BaseTools: Add '--quiet' option to GetMaintainer.py script Philippe Mathieu-Daudé
2019-10-16 14:09 ` [PATCH 3/3] BaseTools: Add script to help git-send-email pick addresses to cc Philippe Mathieu-Daudé
2019-10-16 14:12 ` Philippe Mathieu-Daudé
2019-10-16 14:49 ` [PATCH 0/3] BaseTools: Add a script to use with 'git-send-email --cc-cmd' Laszlo Ersek
2019-10-16 15:18 ` Leif Lindholm
2019-10-16 16:50 ` Philippe Mathieu-Daudé
2019-10-16 18:30 ` Stefan Hajnoczi
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-list 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=08650203BA1BD64D8AD9B6D5D74A85D16154CB80@SHSMSX104.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/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