Folks,
I have the need at times to just grab some files from the repository to serve as samples, instructions etc.
What bugs me is the fact I have to supply a path where to put these files (ok), but then this path is being used as the "working folder" for that branch right away.
If I happen to change a few of those files now, Vault Client wants to check them back in.
OK, so I go there and delete the working folder association - but the Vault client (v4.0.5) still insists to list those files in my "Pending Change Set" tab....
Why can't there be a "just grab files" command which will copy some files to a specified location, but does *NOT* create a working folder association? Or why can't I delete the working folder association and then Vault STOPS bugging me about checking those changes back in? (don't want to - just grabbed the file to tinker around).
Any ideas?
Just getting some files from the repository....
Moderator: SourceGear
Yes, thanks, that's what I'm doing - but if I specify "c:\temp\test", then the files are grabbed and stored there, and "c:\temp\test" is now the Working Folder for that item in the Vault repository and won't ever go away.......Beth wrote:Use the Get Latest command and change the path that is specified. You can perform a Get out to anywhere.
That's what I'm trying to find out - how can I grab some files to an arbitrary location WITHOUT setting the working folder of that Vault $/..../...../.... folder to that temporary disk folder I specify as target........
Marc