Community
Participate
Working Groups
Hi, if I modify a file I get added to editors list. If I close the file without saving I remain listed as editor. This info is visible only in the cvs editors view, that I usually do not use very often, or by the small man icon. I think one solution is to remove the edit if the file is closed without saving. Another one is to add an option to synchronize view to also show file in edit state (only edited by current user or by everyone). So when you commit new changes you are sure not to leave something "locked".
The same happens when: - you organize import in a file where imports are already ok - if you format an already formatted file - if you make a refactor->rename, ask for preview and then cancel the refactor (here all files involved in the refactoring are marked edited). The problem is made worst by the fact that the cvs editor does not support refresh, column sorting, right click to unedit, visualization of file icon (so the be able to see if this is a real edit (with black box with white star) of a false edit.
This bug has not been touched for 2 years. Closing as WONTFIX. Please reopen if you feel this is still an important issue.
I would like to see the status of this changed back to an open issue. I work on a large project which uses cvs for team working and stale edit locks can be very irritating. The solution that uses the synchronize view seems the best one to me.
Reopening
Reopening on request. However, there is currently no plan to address this issue.
It's an important issue for me as well, actually some developers in our development team sometimes come to ignore "old" edits because they know that there are a lot of stale ones. I do think that the synchronize view solution is the best as well because it leaves the choice to the user instead of performing automatic unedits which could be wrong, and it would provide a quick view of all currently edited files that haven't really been touched. This could be activated through a special option in the synchronize view so that "normal" users would not be bugged by this new function?
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
