SourceGear Support

Ah... I'm back and wondering why a 'refresh' is not identifying all changed files so I search on "Vault recursive refresh" and this is the first hit Google gives me. ;) This time the 'read only to force checkout' strategy is not useful. I have to develop on one host and use Vault on anothe...

We've recently upgraded to Vault 9 Pro (9.0.0 30452) and I am trying to merge two branches this morning. I am really having a difficult time with this. There are files that have been modified in only one branch and only some of the changes are making it to the destination. I've merged twice so far a...

Hi Beth, Thanks for the tip. I already reorganized my directory to avoid duplicates so I cannot try your suggestion at the moment. I did check at the time to make sure I had not added one of the directories twice and that was not the case. I did not think to try to add/commit them one at a time. tha...

Given a structure (setup more or less by STM and IAR tools) proj/Inc proj/Src I'd like to add a bunch of files related to say blah. I added directories proj/Inc/blah proj/Src/blah Vault Pro 9 is unable to commit files in these directories because the 'blah' part of the path name is duplicated betwee...

Hi Beth,
I got your email and replied. I got the same response. It looks like I'm getting caught in a spam trap. "Bulk email"

thanks,
hank

Done - thank you for the quick reply. ... Maybe not: Delivery to the following recipient failed permanently: support@sourcegear.com Technical details of permanent failure: Message rejected by Google Groups. Please visit http://mail.google.com/support/answer/188131?hl=en to review our Bulk Email Send...

Good morning, I called up the history of one branch this morning (call it A) and saw that commits I made to branch B were listed in the history for A. I pulled a subsequent copy of B and examined the code to insure that the changes had not been applied there. They had not. I examined the history for...

Hi Beth, Thank you for your reply. Here is what I did. 1) Renamed the top folder in my working directory. It held 567. 2) Right clicked the folder (in Vault), and selected "Show History..." and checked the radio button for "View folder history by version." 3) Selected the version...

Hi folks, I started with a bit of a mess up this morning. I ran our startup code configuration tool which updates a bunch-O-source files. I wanted to isolate the config changes to one commit so I committed (to trunk). Unfortunately I was reminded that this is a test and should not have been committe...

Hi Beth,
Thank you for the tips.

I need to go back to a previous version of our code, make a minor change and build. I cannot see how to do that. The context menu and main menu items all seem to refer to the most recent version. Ideally I think I should branch the older version, make the change and then (if desired) merge the chang...

Hi Beth,
Thank you for the quick reply. It sounds like Shelve is the operation I want.

best,
hank

Hi folks, I've reviewed the material at http://support.sourcegear.com/viewtopic.php?t=9 and http://download.sourcegear.com/misc/vault/help/client/workingwithsharesandbranches.html and I don't think I am getting it. My particular situation at the moment is that I have made a bunch of changes to files...

I see now. Baseline is "In Client Cache Folder." (Which is "In User Local Settings Folder.") At present Concurrent Development Style is set to (all boxes unchecked) and drop down is "Make all files writable." I can report that the behavior "files marked as edited b...

Hi Beth, I may not have reported the problem accurately. I thought I had seen situations where Vault did not recognize changed files. Right now I am looking at the Vault screen and have performed the following operations: Hit the refresh icon in the toolbar. Note that a file I just edited is not lis...