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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html