History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: IDEA-18922
Type: Usability Problem Usability Problem
Status: Open Open
Assignee: Irina Chernushina
Reporter: Patrick Wright
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
IDEA: Feedback

CVS: would like easier way to handle rollback on unchanged local files

Created: 31 Jul 08 12:28   Updated: 11 Aug 08 17:10
Component/s: Version Control Integration. CVS

Environment: Java 6 on Ubuntu 7.10.

Build: 7,925


 Description  « Hide
I find that I regularly have files which are marked as "changed" in the Changes tool, but which on a compare show as having no differences. I suspect this is because I opened the file, changed something, then undid the change; maybe just the timestamp is being compared. Although it causes no harm, when I'm working on a set of changes, these "false positives" throw me off, since I think that a file has been modified when it hasn't. I have to periodically sweep through and rollback the unchanged files. This is a minor issue but happens to me several times a week and is tiresome.

One way to reproduce this: open a file, type a space, save, then undo. It should appear in the changes window.

When I have a number of changes pending locally, I routinely go through them and organize them for checkin. These "false positives" take a little more time than I'd like--I have to wait for a diff, then hit F7, find no changes, close the diff dialog, then open the context menu and choose Rollback, then confirm the rollback.

Enhancement: on the diff dialog, if there are no differences, highlight this in some way and offer a rollback option. Don't put up another confirmation dialog.

Actually, in the diff dialog, having a greater emphasis on the number of changes in the file would help--this is one reason this problem is a hassle: the count of diffs is in fairly light text on the status bar at the bottom of the window.



 All   Comments   Work Log   Change History      Sort Order:
Bas Leijdekkers - 11 Aug 08 17:10
I would prefer it if files with no differences with the repository were not marked as changed at all. This means the changed marking should be removed if the change is undone in some way (either by editing or invoking undo). The Subversion integration already works this way.