Bug 137076 - [Repo View] Prompted that location has changed and encoding change lost
Summary: [Repo View] Prompted that location has changed and encoding change lost
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on: 137075 137073
Blocks:
  Show dependency tree
 
Reported: 2006-04-17 16:37 EDT by Michael Valenta CLA
Modified: 2019-09-06 16:17 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 2006-04-17 16:37:35 EDT 
If I look at the server encoding preference page but don't change anything and then change information on the connection page, I get prompted that the server encoding change was lost.  Since I didn't change it, I shouldn't get prompted. Ideally, if bug 137075 is fixed, this becomes a non-issue.
Comment 1 Tod Creasey CLA 2007-03-29 09:04:30 EDT 
Can you give steps to replicate please?
Comment 2 Michael Valenta CLA 2007-03-29 09:17:39 EDT 
Open the Properties on a CVS Repository location, select the Encoding page and then select the Connection page. On the Connection page, make a change to the connection info. At some point, you will get prompted that the encoding has changed. I'm not sure if bug 137073 would fix this though.
Comment 3 Tod Creasey CLA 2007-03-29 14:11:03 EDT 
It didn't appear to fix it for me.
Comment 4 Michael Valenta CLA 2007-03-29 14:46:28 EDT 
Then why are you closing this bug? We have some issues on the CVS side that cause this. It turns out that a fix for bug 137075 would make this bug irrelevant but, since that bug isn't fixed, I would like to leave this one open.
Comment 5 Tod Creasey CLA 2007-03-29 14:49:59 EDT 
Sorry - must havce slipped when commenting.
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:17:39 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.