This is to document a little quirk with CLC GETVERSION. If I run it like this:
vault getversion -useworkingfolder 2 $/Dev/Project c:/tmp/wc
... and then look at the folder in the GUI client, the file statuses are all "Edited" even though Local Version and Remote version are the same and there are no differences. This happened because I was scripting with Ruby, whose Dir.pwd method returns a path with slashes even on Windows. The GETVERSION command worked and put the files in the right place, but apparently Vault's internal state is not understanding that c:/tmp/wc and c:\tmp\wc are the same working folder.
The moral is to specify absolute paths with backslashes as the destination_folder on Windows if you want the file status to work correctly.
(This is with 4.0.6.15954)
Files are "edited" after GETVERSION
Moderator: SourceGear
Re: Files are "edited" after GETVERSION
Have you checked to see if the timestamps are the same? If one isn't using CRC's to determine differences, then a timestamp change can be seen as a change to the file.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Files are "edited" after GETVERSION
I've looked at the file times and tried all the options for -setfiletime. The only thing that seems to give the right status is an absolute path with proper backslashes.
Re: Files are "edited" after GETVERSION
Thanks for the update.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support