frameworks/projects/advancedgrids/bundles/en_GB/datamanagement.properties mistakenly had svn:executable set to * in the SVN repo. I'd guess that any files actually in the Git repo that have mode 100755 and shouldn't are due to the same problem originating from incorrect SVN properties. We can simply change their mode and commit new versions with mode 100644. (Any volunteers?)
With frameworks/flex-config.xml and modules/asc/src/java/macromedia/asc/util/Version.java, we have a different issue. I believe they have the right file mode in SVN and in the Git repo, but our build scripts are changing the file mode to executable without needing to do so. - Gordon -----Original Message----- From: Dasa Paddock [mailto:dpadd...@esri.com] Sent: Wednesday, April 03, 2013 4:47 PM To: <dev@flex.apache.org> Subject: Re: How to get a clean working tree for flex-sdk $ 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 > >
