Bug 204464 - Moving branch tags should provide warning
Summary: Moving branch tags should provide warning
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.2.2   Edit
Hardware: PC Windows XP
: P4 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-24 11:00 EDT by Brian Young CLA
Modified: 2019-09-06 16:17 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Young CLA 2007-09-24 11:00:26 EDT
In Eclipse 3.2.x the ability to move branch tags was surfaced in the UI.  Previously this was not the case even though other CVS clients provide this functionality.

A warning should be displayed to the user when attempting to move branch tags that explains the dangers of doing so.
Comment 1 Tomasz Zarna CLA 2007-10-08 07:32:16 EDT
If you look for that topic in Eclipse Help you will find a section named "Moving version tags"[1]. In the first paragraph there is a warning which informs that you should be cautious when moving tags. If it's not enough in your opinion, we could think about adding some extra warning in the UI

[1]http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.platform.doc.user/tasks/tasks-105c.htm
Comment 2 David Brown CLA 2007-10-08 11:14:03 EDT
What we are really looking for is a warning message at the time that there is an attempt to move a branch tag such as: "You are attempting to move a branch tag.  Do you really want to do that?".
Comment 3 Szymon Brandys CLA 2008-05-09 04:23:05 EDT
Mass update - removing 3.4 target. This was one of the bugs marked for
investigation (and potential fixing) in 3.4 but we ran out of time. Please ping
on the bug if fixing it would be really important for 3.4, and does not require
API changes or feature work.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:17:03 EDT
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.