Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 29413 - Decorators show directory has updated files, replace w latest doesn't remove decorator.
Summary: Decorators show directory has updated files, replace w latest doesn't remove ...
Status: RESOLVED DUPLICATE of bug 29026
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-VCM-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-13 16:35 EST by IH CLA
Modified: 2003-01-14 08:46 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description IH CLA 2003-01-13 16:35:39 EST
Decorators show directory has updated files, replace w latest doesn't remove
decorator.  No files are highlighted in the directory.  Synch with repository
reports same as source.

cvs update -C -d -P "/directory"

I turned off prune empty directories and then issued the replace with latest. 
The decorator turned off and a directory was created with no files inside.  I
then turned prune empty directories back on and replace with latest.  The
directory was pruned and the decorator remained off.

This is using M4
Comment 1 IH CLA 2003-01-13 16:51:56 EST
Despite the decorator being removed the parent's decorator remains on. 
Replacing the parent with latest from repo with prune directory flag on turns
the sub directory decorator back on.  Replacing the parents with prune directory
off removes all decorators.  Then replace with latest with the flag off again
returns the decorators.  

Neither compare with latest or synch picks up any differences.
Comment 2 IH CLA 2003-01-13 17:02:27 EST
I think this has to do with some invalid state because I can't repro on my
co-workers M4 version.
Comment 3 Michael Valenta CLA 2003-01-14 08:46:30 EST
This bug has been fixed

*** This bug has been marked as a duplicate of 29026 ***