On 06/15/2011 04:56 PM, Erik Faye-Lund wrote: > On Wed, Jun 15, 2011 at 1:04 PM, viresh kumar <viresh.kumar@xxxxxx> wrote: >> On 06/15/2011 04:10 PM, Jakub Narebski wrote: > Sounds like you should try "git config core.filemode false": > > "core.fileMode: > If false, the executable bit differences between the index and > the working copy are ignored; useful on broken filesystems like FAT" > > (from from http://kernel.org/pub/software/scm/git/docs/git-config.html) > . > On 06/15/2011 04:59 PM, Jakub Narebski wrote: > On Wed, 15 June 2011, viresh kumar wrote: >> On 06/15/2011 04:10 PM, Jakub Narebski wrote: >>> viresh kumar <viresh.kumar@xxxxxx> writes: > Ah. This is caused by the fact that FAT doesn't store executable > permission. > > So beside setting `core.symlinks` to false, you would have also set > `core.filemode` to false (and perhaps also `core.ignorecase` to true). > > You might also want to set `core.ignoreStat` to true to try to increase > performace. > > P.S. git-bundle ddidn't work? didn't tried that. :( > Guys, thanks for your inputs. core.filemode was new to me. I tried to resolved issue in some other way. I have tarred kernel before copying to memory stick. And after untarring kernel on windows, file permission are not changed for all files with permission 644 originally. There are some files in kernel whose permissions are 755 and they are converted to 644. And are shown in git status as _modified_. I got rid of them with core.filemode as false, but there is one more issue, as pointed out by Andreas. There are few files in kernel with same file name but in different _cases_ (one in caps and another in small.) and so i am getting issues with these now. And don't have any idea how to get rid of that? And why does kernel have such file names at all? -- viresh -- 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