Release Notes

The performance improvements in the Pending Changes view introduced in 5.4.15.604 are now available and public.

Now, the submodules and the xlinks are synchronized by the GitSync. The Git submodules are converted into Plastic xlinks during the pull and the Plastic xlinks are converted into Git submodules during the push.

The .gitmodules file is not synchronized as a normal file. It is handled on a special way. It is not pulled to Plastic SCM since it is only needed on Git to handle the submodules (is a metadata file). It is regenerated during the push, according to the xlinks info.

Remarks: the content is generated by the sync operation, so the manual editions on this file will not be preserved during the push.

Please note that before synchronizing a repository with xlinks or submodules, the target repositories must be synchronized.

In order to synchronize a repository with xlinks/submodules the mapping information must be added on the gitsync configuration file(gitsync.conf). This information is added on the submodules section with the following format:

git_repository_url -> plastic_repository_spec [writable:true|false] [relativeserver:true|false]

If the submodule must be converted to a writable xlink, the writable field must be included as writable:false. If the writable field is omitted or if it is set to false, the xlink will be created as readonly.

If the submodule must be converted to a xlink with a relative server, the field relativeserver must be included as relativeserver:true. If the relativeserver field is omitted or it is set to false, the xlink will be created against the Plastic repository server as non-relative xlink.

The following is an example:

[submodules]

git://localhost/code -> code@localhost:8084 writable:true relativeserver:true
git://localhost/doc -> doc@localhost:8084 writable:false relativeserver:true