![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: Compare Functionality in Synergy/CM Topic Summary: Created On: 2-Jun-2006 15:05 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I have a question in regards to using the 'Use Version' and compare in Synergy/CM.
We are currently using Synergy/CM 6.3.3285. When a developer views a version which they are not using, the EOL Delimiter is 0D 0D 0A (CR CR LF) but when they use the same version (parallel) that they are using, the EOL Delimiter is 0D 0A (CR LF). Thus when you compare these versions the whole file shows change. Questions: Why is using one version removing a CR (0D)? How did an extra CR (0D) get inserted during a migration? If anyone has experienced any of these situations and has a short, medium and long term solution, please advise. Thank-you very much, Dan Schulz Computer Systems Analyst - EKM Communications Security Establishment Ottawa, Ontario. dan.schulz@cse-cst.gc.ca |
|
![]() |
|
![]() |
|
Hm, that really looks strange! Are you using a Unix server and Win clients and are you sharing files using Samba?
We had something similar to this when sharing files with Samba. Windows uses a 2-byte EOF (0D0A) and Unix uses a 1-byte EOF (0A). In some circumstances, we got files with lines terminating at 0A0D0A. These were Unix files miss-converted into Windows format with a "double EOF" (Unix+Windows). Ok, your EOF looks quite different. But maybe it results out of a failed conversion? Hope, I could give you a hint. |
|
![]() |
Telelogic SYNERGY
» SYNERGY/CM
»
Compare Functionality in Synergy/CM
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.