Bug 62597

Summary:	[Tags] Enter tags directly without using "Configure tags" dialog
Product:	[Eclipse Project] Platform	Reporter:	jens <jens.bensing.ext>
Component:	CVS	Assignee:	platform-cvs-inbox <platform-cvs-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	enhancement
Priority:	P5	CC:	will
Version:	3.0	Keywords:	helpwanted
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description jens

2004-05-18 03:41:45 EDT

shouldn't it be possible to enter a tag directly without using the 
"Configure tags" dialog when merging, tagging, etc.?
I.e. when I have files on a branch which only exists on the branch and not 
on head (all files of the branch are incoming additions), how can I merge 
the branch into head? 
I can neither select the version tag nor the the branch tag itself, 
because the revision on head is in attic (or state: "dead") and therefore 
there is no revision from the target branch (here head) in the local 
workspace to retrieve the tags needed for the merge.

- maybe the easiest way is to add a input field to the "Configure tags" dialog

Comment 1 Jean-Michel Lemieux

2004-05-18 09:03:45 EDT

*** Bug 62595 has been marked as a duplicate of this bug. ***

Comment 2 Jean-Michel Lemieux

2004-05-18 09:20:57 EDT

The workaround is to open the repositories view, select the project in HEAD that
contains a branch that can't be found and select "Add to Branch List" from the
context menu. This will add the branch name and you can use in the merge,
compare dialogs.

I agree that it would be better though to have a text input field.

Comment 3 Michael Valenta

2006-03-30 15:44:58 EST

*** Bug 133939 has been marked as a duplicate of this bug. ***

Comment 4 Eclipse Webmaster

2019-09-06 15:30:11 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.