SourceGear Support

Usually when I merge branches, one of my first steps is to sort the pending change on the Details column, and show differences on all of the Size Unchanged ones (just to make sure that there weren't any changes) and undo those checkouts. That's what I do too. However, it's a real pain, and somethin...

Can't this be done with keyword expansion, with the Log keyword?

Jeff, would it help here if the merge wizard didn't check out files in CVS mode, and just modified them? This way the CRC could be used to detect that the files weren't modified, and eliminate them from the pending change set.

According to Linda, this is a known bug in 4.1.1.

That's true, but clicking once on the header is faster than bringing up the dialog, going to the sort tab, changing the proper sort, and hitting OK.

The reason that the headers don't sort (according to one of the developers a few years ago) is that this is a virtual list, and if the query results in more than a given number of rows, only some of the data is returned at the beginning. The rest of the data isn't loaded until it is needed. Having s...

Ian, I've wanted this for a long time. I don't think I've ever seen this work. If it did, that would be great.

You can branch from any point in history, not just the latest. Can you just branch from the point before that changeset?

This is what we use to make our build number out of the transaction ID. $vaultexe = $ENV{'VAULT_EXE'}; $vault = $ENV{'VAULT_TRUNK'}; $commandline = "\"$vaultexe\" versionhistory -rowlimit 1 -datesort desc -norecursive -excludeactions label -repository \"Default Repository\" ...

Since you can branch from any point in time, we don't create a branch until we need to maintain two different code trees at the same time.

Unless something has changed, groups don't do anything if folder security is disabled.

We use Visual Build Pro for our scheduled builds. We use a homegrown solution for our continuous builds.

You don't have to gave the entire team on one or the other. This is a per-user setting, and it works just fine with some people checking out before editing files and others not.

If you don't have either of them on disk, you should be able to do a history query on on folder, and from there do the diff to the other repository folder. This would download all the files to temp directories and run the diff on those folders.

Oh, and in case this is actually the first time this was logged, add my vote too. I've been wanting the context menu on the search and pending change set panes to include everything in the menu from the regular file pane since we started using the product.