Anders Kaseorg [off-list ref] writes:
On Fri, 7 Jan 2011, Junio C Hamano wrote:
quoted
The change needs to come from gitk repository, so I'll leave it up to Paul
;-)
No, the script has always been executable in gitk.git. The patch should
be applied directly to git.git to bring the two repositories in sync.
If that is the case perhaps the next pull will fix that ;-)
On Fri, 7 Jan 2011, Junio C Hamano wrote:
If that is the case perhaps the next pull will fix that ;-)
Nope. There’s nothing to pull; the current gitk.git master was already
taken by the last pull. Even once there are commits to pull, the common
ancestor will be 6758ad94, in which the script is executable, so the
script will remain non-executable in the merge result. (And you can see
for yourself that the last 28 pulls since 62ba5143 haven’t added the
executable bit.)
The point is that 62ba5143 introduced a change to git.git that wasn’t in
gitk.git, and that change will remain in git.git until it’s undone in
git.git.
Anders