calbzam

Hi, You are right. If you just type, "Yes", does it work? Regards, Carlos.

- Are you using the sync view? From this view, you can select the branches to sync/replicate so you don't always need to clone the full repo: https://www.plasticscm.com/documentation/gui/plastic-scm-version-control-gui-guide#Chapter23:TheSynchronizationview - Also we have a feature to support no-data clones. This way, you only get the metadata and the data is downloaded on demand from the central server. http://blog.plasticscm.com/2017/11/nodata-secret-sauce-of-lighter-clones.html Regards, Carlos.

Hi, You cannot revert the root item of the workspace to a previous revision. In order to do that, please open the branch explorer (or changesets view) --> right-click the selected changeset --> "Switch workspace to this changeset". Regards, Carlos.

Plastic SCM supports partial (no-data) replicas. Could you check if it helps in your workflow? It's very useful for distributed environments. http://blog.plasticscm.com/2017/11/nodata-secret-sauce-of-lighter-clones.html Regards, Carlos.

Hi, As you pointed, the GitServer feature is not still available for cloud repos. It's in our roadmap. I will update this thread as soon as we have more news. Your feedback is appreaciated. Regards, Carlos.

Hi, If you include: .vs I think Plastic thinks this is a file extension (.txt, .bin...). We have a blog post explaining some details about the ignore rules: http://blog.plasticscm.com/2014/11/configuring-ignored-items-on-your.html Regards, Carlos.

Could you attach the "ignore.conf" file? Is the file already under version control? In that case, the ""ignore.conf" wont' help (it only works for private items). You will need to add the folder to the hidden changes list. Regards, Carlos.

Thanks for the update. I'm afraid you will need to re-create the Xlink selecting the writable flag. Regards, Carlos.

Sorry, I'm afraid this is a known issue. We have already generated your Personal license. Regards, Carlos.

Thanks for the update!

Hi, If you drive to the branch explorer, could you edit the date range? There maybe be old branches that are being filtered by the default date filter. You can also take a look into the changesets/branches views. If you drive to the "Workspace explorer" and click "Update workspace", isn't it nothing to update in the "/main" branch? Regards, Carlos.

Hi, - If you run "cm status --private", you should get a list of the private items not the including ignored items. - In the "Pending Changes" view of the Plastic GUI --> Options, you can customize the changed items to be tracked. You can select "private files" and unselect the rest of the changed items so they don't appear in the list. Regards, Carlos.

Hi Lazlo, If you are using a recent version, each help item will only be shown at most once a day. Is this the behavior you are seeing? These panels a useful not oly for new Plastic users but also in some complex merge scenarios... Anyway, your feedback is appreaciated. Regards, Carlos.

"Merge options" is not a pop up but a button you need to click to change the "Ignore emrge tracking" setting: You can only delete a changeset if it's the last changeset of the branch. Regards, Carlos.

In your screenshot, I can see you already performed the cherry-pick. In that case, please delete the result changeset and repeat the same cherry-pick operation but now selecting "Ignore merge tracking" in the merge options. I think the blog post is not very clear about that so sorry for the inconveniences. Regards, Carlos.

Hi, From the blog post: Cherry-pick (ignoring traceability) the subtracted changeset (purple merge link). Merge from the task branch again (green merge link). It's important to selecting "ignoring traceability" when performing the cherry-pick opeartion. I think it could be the problem. Regards, Carlos.

We have just released the fix that should help with this issue: Regards, Carlos.

Just as an update, they were having a connection profile configured for a different user. Regards, Carlos.

Hi, If you rename a branch and there are other developers whose workspaces are pointing to the original branch name, they will get an error if they try to checkin changes because the checkout branch name doesn't exist anymore. They will need to update the workspace selector to point to the new branch name. Regards, Carlos.

Hi, Could you check if your disk in macOS is case insensitive? In the following link they explain how to cehck it. https://apple.stackexchange.com/questions/22297/is-bash-in-osx-case-insensitive You can also open a macOS Terminal and try to create a "foo.txt" and "Foo.txt" files in the workspace path. Regards, Carlos.

Hi, Is it posible that this file was initially commited on Linux and now you are reverting on a Windows machine? It could be the explanation. Regards, Carlos.

Have you modified any configuration: client.conf... on the server machine? According to the error message the user you have currently configured in this machine doesn't have enabled permissions. It makes me thing that you have somehow changed the user. If the issue persists, you can reach us at support@codicesoftware.com and we can arrange a GoToMeeting session. Regards, Carlos.

The "client.conf" path is: C:\Users\<YourUser>\AppData\Local\plastic4\client.conf Regards, Carlos.

The "cm diff --help" command has a "--download" option. eg: cm diff cs:19 cs:23 --download="D:\temp" Regards, Carlos.

Could you manually copy the "client.conf" from the working machine to the rest? This is the file where the credentials are stored. Regards, Carlos.