| Summary: | staging view shows files which have no changes | ||
|---|---|---|---|
| Product: | [Technology] EGit | Reporter: | Gil Barash <scobido1984> |
| Component: | Core | Assignee: | 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
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). Is this still valid? 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). 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. Haven't seen this myself. The original report was probably caused due to CRLF issues, where there were some fixes in the last releases. |