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

Bug 185749

Summary:	[Change Sets] Eclipse Synchronize Incoming CVS Change set is wrong
Product:	[Eclipse Project] Platform	Reporter:	Jaap Jansma <jaap>
Component:	CVS	Assignee:	platform-cvs-inbox <platform-cvs-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	CC:	eclipse
Version:	3.2.2	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Jaap Jansma

2007-05-07 08:51:34 EDT

Build ID: M20070212-1330

Steps To Reproduce:
1. Import a project from CVS (head)
2. Create a branch (Branch_01)
3. Import the same project from CVS (head)
4. Create another branch (Branch_02)
5. Import a project from CVS (branch: Branch_02)
6. Remove a file in Branch_01
7. Commit this remove to CVS
8. Remove the same file from Branch_02



More information:
When you synchronize with CVS and the same file is removed from several branches, the changeset is incorrect and shows the commment from a remove from a different branch.

Comment 1 Michael Valenta

2007-05-07 15:24:12 EDT

There are a few issues with incoming change sets. Unfortunately, we haven;t had the manpower to address these in 3.3 and it is not clear we will be able to do so in the foreseeable future. Patches will be accepted.

Comment 2 Görge Albrecht

2008-09-25 08:11:12 EDT

We have a similar problem.
Could be summarized as "changeset is incorrect and shows the commment from a different branch when comparing with 'Another Branch or Version'."

Comment 3 Eclipse Webmaster

2019-09-06 16:17:40 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 4 Eclipse Genie

2021-09-11 16:35:18 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. 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.