Problem:
Sometimes you checkin changes that aren't necessarily corelated. Well, yes they belong to the same fix, but you could easily revert one change without the other.
When people don't have the habbit to checkin every now and then, they need to checkin when they're done. Most of the time, this checkin contains more than one change.

In the unexpected event of a new bug, that was checkedin with these changes, it's hard to revert that one change that's causing the issue.

Suggested solution:
This problem could be solved if there was a way to split existing changesets into new changesets. It would be easy then to substractive merge the one change.

I think it should be possible to select the files and secific changes in a file to split into a new changeset.
The new changeset would have to be placed right between the original one and everything thats roots to it.

People were asking for a solution for this problem for a long time now and this is what I came up with this morning.

It would be a killer feature! Maybe for version 6.1? ;)

The current checkboxes in the regular plastic client are borderline unusable from both a usability and visual feedback perspective.

By contrast, the Gluon client hits the mark with its checkboxes. It has much larger checkbox size that are far easier to click, and checkboxes that are coloured in when checked as opposed to a tiny black tick mark that is practically impossible to see when dealing with a larger changeset (I've lost count now the number of times I've checked in files I didn't intend to include, simply because the client decided to check them automatically and I couldn't tell).

Having the same checkboxes in both clients would help remarkably with the checkin process

The new "multi-screen diff" in Plastic 6.0 is excellent. It was introduced in 6.0.16.884; if you have the Plastic SCM main window open on part of your screen, and open one diff window on another part of your screen, then the diff window's contents will change when you move around in the Branch Explorer.

(Slightly related uservoice: https://plasticscm.uservoice.com/forums/15467-general/suggestions/15615156-show-diffs-in-branch-explorer-and-changesets-views )

However, this has a few flaws related to cases where you don't want the "Diff changeset" window to change. To stop the Diff from updating when you click a changeset, you need more than one Diff window open. This is OK in theory, but in practice it works like this:

* If you double-click a changeset to open the 2nd Diff window, the double-click is ALSO interpreted as a single-click which updates the contents of the 1st Diff window.

* If you right-click a changeset to choose something in the context menu, this is ALSO interpreted as a single-click which updates the contents of the 1st Diff window.

* One of my coworkers is going nuts over this and would like an option to completely disable the auto-updating of Diff window content.

We need to be able to do a diff on a repository on a server (without workspaces) and then get the OLD version of a file through any xlink.

cm diff OLD NEW

You don’t get the path on the remote repository from a diff on current repository.

If I do a cm diff in the first repository, There is NO path information through the xlink. And ALL the information is related to the NEW changeset.

So you can not do a simple diff using the FIRST repository’s information:

$ cm ls '/one/two/My link with spaces/bird/file1.txt' --tree='24@00000000_99_TEST_REPO_3a@myhost:8087' --format="{revid}"

Can't resolve the selector for the item /one/two/My link with spaces/bird/file1.txt

Because all the info is for the FIRST repository, not the REMOTE repository xlinked to.

Doing a diff on the FIRST repository currently gives the following with NO information about the xlink:

$ cm diff '24@00000000_99_TEST_REPO_3a@myhost:8087' '26@00000000_99_TEST_REPO_3a@myhost:8087' --format='PATH:{path} STATUS:{status} TYPE:{type} PREVID:{parentrevid} REVID:{revid}'

PATH:"/one/two/My link with spaces" STATUS:C TYPE:X PREVID:-1 REVID:-1
PATH:"/one/two/My link with spaces/bird/file1.txt" STATUS:C TYPE:F PREVID:463 REVID:474

What is needed is the same NAME output variable as what ‘cm ls / -R’ provides, so you can get this using the diff command:
$ cm diff '24@00000000_99_TEST_REPO_3a@myhost.net:8087' '26@00000000_99_TEST_REPO_3a@myhost.net:8087' --format='PATH:{path} STATUS:{status} TYPE:{type} PREVID:{parentrevid} REVID:{revid} NAME:{name}'

PATH:"/one/two/My link with spaces" STATUS:C TYPE:X PREVID:-1 REVID:-1 NAME:My link with spaces -> xlink -> /dog/cat 42@00000000_99_TEST_REPO_2@myhost.net:8087