Community
Participate
Working Groups
Build Identifier: 1.1.0.201109151100-r If there are differences in the executable bit of an entry in the tree, checking out a branch results in an index with staged changes. The native git client behaves differently, checking out the same branch results in a clean working directory. Reproducible: Always Steps to Reproduce: 1. Create a new git repository (ensure core.filemode is set to true) 2. Create and add a file (use chmod 644) 3. Commit the file addition 4. Set the executable bit (chmod u+x) on that file 5. Commit that change 6. Create a branch pointing to master~1 (i.e. with the changeset without the executable bit set) 7. Use jgit to checkout the new branch Expected Result: HEAD should point to the new branch, the working directory is clean Actual Result: HEAD points to the new branch, the working directory is dirty with the filemode change to be commited.
Created attachment 207005 [details] Script to setup a test repository. The attached script can be used to set up a test repository in order to reproduce the behaviour.
Proposed fix pushed to: http://egit.eclipse.org/r/#change,4912
+1, this is a not-so-cool interop problem with our windows friends :)
ah, i was wrong.... this affects all platforms of course. happens on linux the same as on windows.
i think this has another side effect: i cannot rebase anymore, as long as i have such a filemode change, and i just get a "rebase failed" message without any further details.!?
can somebody close this, it was fixed by Change-Id: I224602d68228eb419813986807f1eeab77e9c302
merged as ed7b322186a872bdd4f41a1a31554a7e90d74de6
