Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 315878

Summary: Refresh should be integrated with Workspace Refresh
Product: [Technology] EGit Reporter: David Carver <d_a_carver>
Component: UIAssignee: Stefan Lay <stefan.lay>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: glen.84, jens.baumgart, matthias.sohn, mn, remy.suen, robert.munteanu, stefan.lay
Version: 0.8.1   
Target Milestone: 0.9.0-M2   
Hardware: PC   
OS: Linux   
Whiteboard:

Description David Carver CLA 2010-06-05 11:11:53 EDT 
Currently there can be a git status disconnect between eGit and the git repository if the command line is being used.   If items are committed at the command line the status within eGit is still showing files that need to be modifed.

There is a Team->Refresh option in eGit, but this should really be part of the general Refresh process.   So that when a refresh of the workspace is being done, the functionality of Team->Refresh is also run at the same time.
Comment 1 Jens Baumgart CLA 2010-07-14 08:50:43 EDT 
Could reproduce the following:

1. Modify a file using notepad and add it to the index using the command line.
2. After some delay the file is decorated with >*.

">" is wrong since the content of the file does not differ from the content in the
index. Reason for the > decoration is DecoratableResourceAdapter taking the time stamp from the (outdated) Eclipse resource instead of taking the real file timestamp.
Comment 2 Stefan Lay CLA 2010-07-16 08:06:25 EDT 
A fix is proposed at http://egit.eclipse.org/r/#change,1138.

Now the dirty marker is determined from the timestamp of the file on disk. If it does not match the content is compared.
Comment 3 Stefan Lay CLA 2010-08-05 02:46:59 EDT 
Fixed with b50d2355ce2f84c9ce1830b66879859cc70671c0