Bug 14591 - [CVS UI] Replace with latest on version doesn't do what user expected
Summary: [CVS UI] Replace with latest on version doesn't do what user expected
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-VCM-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2002-04-25 07:55 EDT by Jerome Lanneluc CLA
Modified: 2004-03-24 15:19 EST (History)
0 users

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 Jerome Lanneluc CLA 2002-04-25 07:55:07 EDT 
Build 20020423

I had version 242 a project loaded in my workspace.
I chose Replace with... -> Latest from repository. It ensured that all my files 
were from version 242, but at the end this was a noop.

I would expect that it replaces with the latest files released in HEAD.
Comment 1 Kevin McGuire CLA 2002-04-25 10:35:03 EDT 

*** This bug has been marked as a duplicate of 14578 ***
Comment 2 Kevin McGuire CLA 2002-04-25 10:40:32 EDT 
Not a dupe.

We should disable replace with latest since although it does the right thing 
(replace with contents with that tag), it doesn't do what people expect.

Jerome, to do what you want you should do replace with "Tag" and pick "HEAD".
Comment 3 James Moody CLA 2002-04-25 10:54:26 EDT 
Remember, though, that we can now have mixed tags inside a project... we 
shouldn't disable this unless we know that *every* file underneath the project 
is shared with a version.
Comment 4 Kevin McGuire CLA 2002-04-29 13:44:00 EDT 
Post 2.0

Don't know what more we can do here.

Renamed bug from:
   Replace with latest doesn't replace with HEAD contents

to better reflect the problem.
Comment 5 Michael Valenta CLA 2002-09-09 16:22:02 EDT 
Reopening
Comment 6 Michael Valenta CLA 2004-03-24 15:19:03 EST 
We now put the tag in the repalce with menu item so the user can see what will 
happen. We don't prevent the operation because it is possible for a tag to 
move.