$ git ls-files --stage | grep "100755" shows that there are a lot of files that are set as executable that don't need to be, like:
frameworks/projects/advancedgrids/bundles/en_GB/datamanagement.properties --Dasa On Apr 3, 2013, at 4:36 PM, Dasa Paddock <dpadd...@esri.com> wrote: > You can use this to see what the mode is set to for a file: > > $ git ls-files --stage <file> > > --Dasa > > On Apr 3, 2013, at 4:29 PM, Frédéric THOMAS <webdoubl...@hotmail.com> > wrote: > >> I just read the git mode particularities from [1] >> >> In this case, you’re specifying a mode of 100644, which means it’s a normal >> file. Other options are 100755, which means it’s an executable file; and >> 120000, which specifies a symbolic link. The mode is taken from normal UNIX >> modes but is much less flexible — these three modes are the only ones that >> are valid for files (blobs) in Git (although other modes are used for >> directories and submodules). >> >> -Fred >> >> [1] http://git-scm.com/book/en/Git-Internals-Git-Objects > >
