vault GUI and command line differences

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
wes@encomia.com
Posts: 4
Joined: Thu Apr 15, 2004 9:33 am

vault GUI and command line differences

Post by wes@encomia.com » Thu Mar 24, 2005 11:30 am

I'm checking out files via command line and when I do a GET with a -merge overwrite, I've noticed that all the files that are downloaded appear as "edited" in the GUI client.

Mind you both exe's are using the same login account to download the files.

If I do a "get latest version" and specific "overwrite" from within the GUI, it overwrites all the files and they aren't marked as "edited".

Shouldn't the CLC perform the same action?

It seem to think it's a different user and doesn't recognize that the "get" was performed with the same account .

What gives??

EDIT: version 2.0.6

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Post by jeremy_sg » Thu Mar 24, 2005 12:06 pm

Most likely, you're including the -destpath parameter on your CLC get. This parameter will cause the CLC to ignore the fact that you're getting to a working folder and fetch all of the files and replace the files that are there. Removing the -destpath parameter will cause the CLC to get to your working folder, without setting files to edited.

wes@encomia.com
Posts: 4
Joined: Thu Apr 15, 2004 9:33 am

Post by wes@encomia.com » Thu Mar 24, 2005 12:36 pm

jeremy_sg wrote:Most likely, you're including the -destpath parameter on your CLC get. This parameter will cause the CLC to ignore the fact that you're getting to a working folder and fetch all of the files and replace the files that are there. Removing the -destpath parameter will cause the CLC to get to your working folder, without setting files to edited.
that was it! thanks!

Post Reply