Who we are

We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.

If you want to give it a try, download it from here.

We also code SemanticMerge, and the gmaster Git client.

Plastic SCM 4.1.10.404 External Release is out!!

Monday, February 25, 2013 Amalia 0 Comments

This post shows the release notes for Plastic SCM 4.1.10.404 external release. For a detailed listing of all changes, refer to release notes.
Visit Plastic SCM download page to install Plastic SCM. It’s an easy process.
You can suggest and vote for new features on the Plastic SCM Forum page and to tell us what you think about Plastic SCM.
Now, see the full list of new features and issues resolved in this release.

Features

Different Enconding
The DiffTool and the MergeTool have been improved because they now support files with different encodings. The user can choose a different encoding for the three different contributors and also for the merge result file.
On the “Preferences View” you can still set the default encoding. This option will be used when the specific contributors encoding can’t be detected. On the other hand, the custom contributor encoding will not be used when a specific contributor encoding is detected.
If the configured encoding is set to “NONE”, the encoding will depend on the contributors encoding. There are several possibilities:
  • If both merge contributors are having the same encoding the merge tool will use that certain encoding for the result merge file.
  • If only one of the merge contributors has changed the encoding, that new encoding will be used for the result merge file.
  • If both contributors change the encoding, the result encoding will be the less restrictive one.
  • If the encoding is not detected the content will be processed in raw mode
Finally, the UTF-8 encoding by default will not write the BOM field, only if the encoding has been changed to UTF-8 with BOM is when the BOM will be written into the result merge file. The UTF-8 BOM filed is not added by default anymore.

Bugs

Annotate
The annotate operation was throwing an error when the operation was executed for a checked out item located inside an xlink. Now it’s fixed and working.

Enjoy it!

Amalia

0 comentarios:

Subscribe to: Post Comments (Atom)