| Summary: | [synch view] Compares not persisted across workbench sessions | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Johan Compagner <jcompagner> |
| Component: | CVS | Assignee: | Platform Team Inbox <platform-team-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P5 | Keywords: | helpwanted |
| Version: | 3.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | stalebug | ||
|
Description
Johan Compagner
Comparisons are not persisted between workbench sessions. Synchronizations, whether it be a sync, a compare, or a merge, decide if they can be persisted, and pinning is more of a UI hint that the sync view should replace the sync. We have thought about persisting comparisons between sessions, it isn't really all that hard, but we didn't get around to doing it. But I think there is a solution for you, instead of running a comparison against the branch you should run a merge. Merges are persisted across sessions and are three way so that you can see the outgoing/incoming changes easier. We work in this mode all the time, since we have maintenance branches. That would let you monitor the branch for changes are update the files when you want. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |