# [PATCH] Set the executable bit on gitMergeCommon.py. 2 messages from 2006-05-23 to 2006-05-23. Participants: Peter Eriksen, Junio C Hamano. Thread: https://gitlist.dev/t/4253 ## Peter Eriksen, 2006-05-23 08:12 Subject: [PATCH] Set the executable bit on gitMergeCommon.py. Message-ID: <20060523081238.GB4038@bohr.gbar.dtu.dk> URL: https://gitlist.dev/e/20060523081238.GB4038%40bohr.gbar.dtu.dk ``` From: Peter Eriksen Date: Mon, 22 May 2006 15:35:42 +0200 Signed-off-by: Peter Eriksen --- 6465b4c8cc760102ed5771ccded2c02904539475 0 files changed, 0 insertions(+), 0 deletions(-) mode change 100644 => 100755 gitMergeCommon.py 6465b4c8cc760102ed5771ccded2c02904539475 diff --git a/gitMergeCommon.py b/gitMergeCommon.py old mode 100644 new mode 100755 -- 1.3.3.g288c ``` ## Junio C Hamano, 2006-05-23 08:34 Subject: Re: [PATCH] Set the executable bit on gitMergeCommon.py. Message-ID: <7virnx5ec2.fsf@assigned-by-dhcp.cox.net> URL: https://gitlist.dev/e/7virnx5ec2.fsf%40assigned-by-dhcp.cox.net In-Reply-To: <20060523081238.GB4038@bohr.gbar.dtu.dk> ``` "Peter Eriksen" writes: > From: Peter Eriksen > Date: Mon, 22 May 2006 15:35:42 +0200 > > Signed-off-by: Peter Eriksen It makes some sense to make git-merge-recursive.py executable, just in case somebody wants to run it without preprocessing. However, gitMergeCommon.py is a module without the main program. It does not even have the usual "primarily meant to be a library but you could run it standalone" idiom at the end: if __name__ == '__main__': test() So I am not sure if this patch makes sense -- does it misbehave on your system when installed without +x bit? ```