On Fri, Feb 16, 2018 at 10:34 AM, Torsten Bögershausen <tboegi@xxxxxx> wrote: > On Thu, Feb 15, 2018 at 09:24:40AM -0600, Robert Dailey wrote: >> On Tue, Oct 3, 2017 at 9:00 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > > [] >> >> Sorry to bring this old thread back to life, but I did notice that >> this causes file modes to reset back to 644 (from 755) on Windows >> version of Git. Is there a way to `$ git read-tree --empty && git add >> .` without mucking with file permissions? > > No problem with the delay, under the time we had the chance to improve Git: > >>Git 2.16 Release Notes >>====================== >>[] >>* "git add --renormalize ." is a new and safer way to record the fact >> that you are correcting the end-of-line convention and other >> "convert_to_git()" glitches in the in-repository data. > > Could you upgrade to Git 2.16.1 (or higher, just take the latest) > and try with > git add --renormalize . > ? Thanks for the response. Unfortunately I've deliberately been stuck on v2.13 because of [a bug in Git for Windows][1] that hasn't yet been resolved (it's a bug *somewhere*, not sure if it's git related or not). Curly braces in aliases are being stripped which makes newer releases unusable for me. I'll try upgrading on a different machine and see if renormalize works for the case of binary files with file modes set to 755. [1]: https://github.com/git-for-windows/git/issues/1220
