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

Bug 350773

Summary: staging view shows files which have no changes
Product: [Technology] EGit Reporter: Gil Barash <scobido1984>
Component: CoreAssignee: Project Inbox <egit.core-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: minor    
Priority: P3 CC: leachbj, robin.rosenberg, robin, scobido1984
Version: 1.0   
Target Milestone: ---   
Hardware: All   
OS: Windows 7   
Whiteboard:

Description Gil Barash CLA 2011-06-30 03:28:25 EDT
I made some modifications to a file and then deleted them (manually, not using "reset") it would be nice if the staging view could filer-out files which are identical to the files in the repository.
Comment 1 Bernard Leach CLA 2011-07-02 20:11:15 EDT
For resources that are tracked by eclipse (e.g. exist in a project) this should happen automatically when the file is saved or refreshed.  Files outside the projects are not refreshed and a manual refresh is required (see toolbar items).
Comment 2 Robin Rosenberg CLA 2012-08-17 14:29:16 EDT
Is this still valid?
Comment 3 Gil Barash CLA 2012-08-19 01:45:40 EDT
Yes.

I don't think my description was clear, so let me rephrase...

Steps to reproduce:
1. Edit a file which is already in the repository (for example, add a space).
2. Delete that space and save the file (so the file is now identical to how it was before the edit).
3. Open the Git Staging view. You'll see the file.

I understand that each file modified is automatically inserted into the staging list, but the list can be filtered so it won't show files in which there is no point in committing (because the commit would have no difference in it).
Comment 4 Robin Rosenberg CLA 2013-04-17 19:25:11 EDT
Is this an issue in the nightly builds?

I think I've seen this in an unverifiable context with pre 3.0 builds,
but that it was gone with the nightlies a couple of weeks ago.
Comment 5 Robin Stocker CLA 2013-09-29 15:43:33 EDT
Haven't seen this myself. The original report was probably caused due to CRLF issues, where there were some fixes in the last releases.