Bugzilla – Full Text Bug Listing
| Summary: | Commits create perpetually unstaged bogus changes | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Technology] EGit | Reporter: | Nolan Lawson <nolan.lawson> | ||||
| Component: | Core | Assignee: | Project Inbox <egit.core-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | nolan.lawson | ||||
| Version: | 0.11 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Never mind - version 0.12.0.201102160313 seems to have fixed this issue. |
Created attachment 188700 [details] Screenshot of gitk Steps to reproduce: 1) In any git repository, make changes to a file. 2) Right click on the project, choose "Team," then "Commit." 3) Stage and commit the changes by clicking OK. Expected result: Commit is successful, and working directory is now clean. Actual result: Commit is successful, but working directory shows the file as modified and unstaged. Gitk says "local changes checked in to index but not committed." If you try to commit THOSE changes, then the same result happens over and over again. I tried reproducing the bug using Cygwin on the same Git project, and was unable. "git commit -a" works as expected in Cygwin. Only Egit manifests this bug. I'm running Windows Vista x86 (Service Pack 2), and my Egit version is 0.11.0.201102100751.