Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 189663

Summary:	[Change Sets] Conflicting changes should appear in Unassigned category
Product:	[Eclipse Project] Platform	Reporter:	Michael Valenta <Michael.Valenta>
Component:	CVS	Assignee:	platform-cvs-inbox <platform-cvs-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	Keywords:	helpwanted
Version:	3.3
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Michael Valenta

2007-05-29 09:23:22 EDT

In change set mode, conflicting changes should always appear twice, once in an outgoing change set and once in an incoming change set. In the case where the conflict has not been assigned to an outgoing change set, it should appear in the Unassigned category. Currently, the former occurs but the later does not.

Comment 1 Michael Valenta

2007-05-29 09:24:11 EDT

See bug 173138 for background.

Comment 2 Eclipse Webmaster

2019-09-06 16:18:42 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.

Comment 3 Eclipse Genie

2022-01-09 14:48:42 EST

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.