New features in Ellié Computing Merge 2.1

Accessing configurations from many SCC and check-out

You can now connect to SCC / VCS / SCM servers (source code control, version control systems, software change management), such as CVS, SubVersion (SVN), Perforce, ionForge Evolution, Microsoft Visual Source Safe. Since 2.2, several distributed VCS are supported such as Git or Mercurial. Our configurable system allows us to extend easily the list of supported tools, and this on all platforms not only Windows (most competing products with this feature are limited to Windows), please contact-us with a support ticket if you need another tool. For sure, ECMerge is integrable with these tools, for use as a differences viewer and merger. This double entries access allows you to generate reports between configuration stored in SCC repositories, when most SCC have very poor reporting capabilities, while profiting from your SCC tool interface to launch files comparisons.
Our system is built to list folders (with metadata such as size and date when they are available), reading content of files and check-out. All the concepts of branches, labels, revisions, versions, ladders... and so on, are supported. It allows you to access any configuration out of your preferred version control tool. More about this
Check-out (or edition as told in some SCC) is handled so as to allow you edit local files which are matched by a file stored in the repository, this is done by calling your tool and asking it to give write access to the file, preventing potential data loss (some tools do not need this procedure and hence do not have the check-out command).
The check-out feature is integrated with every document write operation, this way saving, applying a patch or simply copying a file may provoque file check-out when it is under a zone of your local file system mapped to a SCC supporting check-out. More about mappings and check-out.

Importing Unix patches

For many versions already, ECMerge allows exporting to Unix patches. It can now import them, i.e., interpret these patches based on an existing version and produce a modified version in place (equalivent to 'patch'), to another place (for example using a SCC source and a local folder as target) and even build a temporary view pre-configured for one of those actions (it allows you to verify the impact of the patch before anything is written... if everything is OK).
The patches are applicable to files and folders. Many 'smart' options are there to detect non-trivial cases (such as moved lines, less context...)...
A 'test' mode exists which parses the patch and tries to find source files but do not actually act, just informing about potential problems. More about importing patches.