Bug 74013 - [Change Sets] RLog fails to get comment in some cases
Summary: [Change Sets] RLog fails to get comment in some cases
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2004-09-15 15:54 EDT by Michael Valenta CLA
Modified: 2021-10-12 18:12 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Valenta CLA 2004-09-15 15:54:04 EDT 
Here's the steps to reproduce

1) Load R3_0 of org.eclipse.team.core
2) Compare with I20040913
3) Enable commit sets and observe that the comment for a new schema file was 
not fetch.

This is probably due to how the tags are used. The same problem does not occur 
if the local is mapped to HEAD instead of R3_0 (I moved the local to HEAD 
using the CVS Utils).
Comment 1 Michael Valenta CLA 2005-03-30 11:44:56 EST 
No time for this in 3.1
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:11:01 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 CLA 2021-10-12 18:12:35 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.