SourceGear Support

Using SOS 4.2 Long, long time SOS user, and I'm now considering ditching it out of exasperation I want to absolutely disable merging. How do I do that? Currently I am getting endless messages such as the one pasted below my sig. I NEVER merge. I don't care about merge. Store this version, dag nab it...

Thanks Jeremy. Er, do you have a tracking number for this dishing dirty XML bug?

**--** Steve

This is probably not the preferred location for this, but this is an easy and vital enhancement request for the next version, or the even next minor release. Using the Vault command-line client to fetch HISTORY, we're getting-back invalid XML, and hence won't load in a DOM, when a developer uses nes...

I sent an email to you yesterday evening, as you suggested, but have not received a reply from you as of yet. Considering that, to get my Diff process started, I right-click on an item in a tree in the Vault UI, it ought to be pretty simple to surface this. In this sense, it really doesn't matter a ...

(Reposting this here because it's not getting any traction in the sleepy DiffMerge section -- It's not really DiffMerge, it's how Vault invokes Diffmerge) We've got a pretty big repository with several branched trees. So far we've had good luck hooking the DIFF process using a wrapper program, but w...

THIS HAS BEEN MOVED TO THE MAIN VAULT SUPPORT SECTION We've got a pretty big repository with several branched trees. So far we've had good luck hooking the DIFF process using a wrapper program, but we've got one snag that looks intractable. In our situation, we sometimes need to bring-down a second ...

It's absolutely, positively AMAZING that a product that uses a back-end database to store mission-critical resources, like those every single one of your customers stores in vault, DOESN'T SUPPORT REPLICATION. Nevermind supporting functional replication, which I can understand, but to not support re...

Thanks Jeff, I'll digest that and report back. You've been very helpful and I appreciate your attention. In a sidebar, I wonder: why is Vault so much less functional than Source Offsite? You see, if we could map more than one Vault folder to the same working folder (like we can with Source Offsite) ...

Unless I'm mistaken, the problem with labels in Vault is - a GET on a label is a (really) buried procedure relative to "Get Latest Version" and - the label is apparently not visible in the History explorer (!?) Then there's the issue of communicating labels, and managing label naming conve...

Hi Jeff, let me explain again, because I don't get the sense that you are listening. 1) Developer A CHECKS-OUT file Foo. It's his exclusively. He'll be working on it, maybe for a while. Say several days. 2) Developers B and C are working on other dependent aspects of the application. So you are tell...

We used to do this all the time with SourceOffsite but Vault apparently does not allow this: Two distinct projects pointing to the same working folder. Here's why we need this: "Project A" contains usual files for source control. "Project A (no clobber)" contains files for develo...

Hi Jeff, thanks so much for the reply. But branching, you see, requires a duplication of the whole project tree or, at minimum, introduces a layer of complexity that we want to absolutely avoid. The goal is pretty simple and, im my experience, universal. * When user A checks out a file, then users B...

First post.... Here's what I need and, if I'm not mistaken, I believe other revision control systems work this way. I need "Pin" to not mean "Freeze". I need to continue incrementally evolving files that are pinned. In my view a "Pin" should be the version returned by &...