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

Starteam Checkout  Mistakenly Says Status Modified

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From [EMAIL PROTECTED]  2003-09-01 19:14 -------
I think I need a more detailed description to proceed with looking at this. 
Also, your StarTeam version is older than any I have access to.

Since both your client and server are Win2K machines, I am assuming that CRLF
considerations are not involved.  Also the whole discussion about "Revision On
Disk" seems to be a false trail, since that is inherently GUI dependent.

I wonder if the problem is not inherent in the operation of checking out to a
label.  Could it perhaps be that StarTeam sees a later version of the file on
disk and therefore assumes that the file is "modified" vis-a-vis the labeled
version you are trying to check out?  Personally, when checking out a labeled
project version through ant, I'd be tempted to start with an empty local
directory tree.  Otherwise, to get a fully correct local tree you must make sure
to also set the createworkingdirs and deleteuncontrolled attributes.  I'd like
to understand more of your use case here.

At any rate I am going to set this to INVALID.  If you can provide me with more
exact details, I will take a further look.  Sorry to take so long on this, but I
have been very busy the past six months.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to