Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 336845 - Commits create perpetually unstaged bogus changes
Summary: Commits create perpetually unstaged bogus changes
Status: RESOLVED FIXED
Alias: None
Product: EGit
Classification: Technology
Component: Core (show other bugs)
Version: 0.11   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-10 11:53 EST by Nolan Lawson CLA
Modified: 2011-02-16 10:37 EST (History)
1 user (show)

See Also:

Attachments
Screenshot of gitk (95.73 KB, image/png)
2011-02-10 11:53 EST, Nolan Lawson CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nolan Lawson CLA 2011-02-10 11:53:45 EST 
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.
Comment 1 Nolan Lawson CLA 2011-02-16 10:37:19 EST 
Never mind - version 0.12.0.201102160313 seems to have fixed this issue.