DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17695.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17695
EOL Makes Starteam Checkout Say Status Modified
--- Additional Comments From [EMAIL PROTECTED] 2003-03-06 22:02 ---
I'm beginning to think this issue isn't EOL related. Instead, I think it might
be that the stcheckout task isn't communicating to the server the Revision on
Disk.
Given: file F in starteam with branch revisions 1.1 and 1.2, and revision on
disk 1 and 2, respecitively. Let revision 1.1 have file size 10 and revision
1.2 have file size 20. Let the tip for file F be 1.2. Let Attach
label mylabel1 to 1.1 and mylabel2 to 1.2. In summary,
for file F
branch revision revision on disk label file size
--- --- -
tip- 1.2 2 mylabel2 20 bytes
1.1 1 mylabel1 10 bytes
Test: If stcheckout grabs the file with mylabel1, I assume the starteam
windows client would report Revision on Disk as 1. However, I'm seeing the
starteam windows client reporting Revision on Disk as 2.
Questions:
1. How does the starteam windows client determine the Revision on Disk?
2. Why is the file Status=Modified? I assume because the file size is 10 and
doesn't match the file size for the tip revision 20.
3. How does the starteam SDK determine if a file is modified?
