Upgrayeddedd

I guess I don't really understand PlasticSCM. Well, it's different to Git and I get that, but I just don't understand how I am supposed to do this. I have made a whole load of changes on a new branch. Well, they started as changes on main and then I checked them into a new branch. I have made several further commits on this work branch. But those just represent different stages of the work. Like committing what I had done so I could continue from home on another PC. This is not unusual workflow. Now I want to separate all this work into different commits that are based on some different aspects of the work I've done. Maybe some of it was fixes for NDepend, some for whitespace cleanup, some bug fixes, whatever. But Plastic seems to want to be all or nothing, I can merge all this work back to main fine, but there doesn't seem to be a way for me to split it into a new set of changesets. And before several people break their fingers trying to bash "hIsToRy ReWrItInG iS bAd" into their keyboards, I am a winner. I am writing history. It can be into a new branch, where in this branch, everything is done in a different order. And nothing is going to be merged back to main from the "broken" work branch, so there's no issue. What I'm looking for is some workflow, how can I use the tools to organise a new set of changesets with my existing changes from the work branch but in a different partitioning, that I can then merge back to main?

I'm getting nowhere with this. I am trying to install this on Ubuntu 20.04, headless. I just need the CLI to work. I got around this GTK or whatever thing, adding the other old repos. But now the problem is that we are on this "cloud" Plastic. clconfigureclient doesn't work any more so I am using cm configure. But it doesn't work no matter what I do. I tried putting <my org>@cloud in for the Plastic SCM server address but ... OK UPDATE, as I was writing this I tried again and now it detected LDAP. It didn't before, it had an error. But now I put my email/pw in and it says it configured the client OK. But when I run cm repo it now says "Error: Connection refused [::ffff:127.0.0.1]:8087" so it is still trying to connect to some local server. I don't know what I am doing wrong now?!? Also, I tried "cm repo list <my org>@cloud" and it asks for unityid/email. I put it in but it just loops back to asking again. ... OK so I tried renaming ~/.plastic4/client.conf but then it said it needed it. So I am running cm configure again, but it complains about an error checking the security mode. Well, I forgot to run it as sudo, now with sudo it seems to go straight to the LDAP thing. OK, a little weird why it needs sudo for that, but OK. Anyway it said it had been correctly configured but then it didn't even bother writing out a client.conf file so it really isn't. ... Update again: OK so it seems that it only creates the client.conf if I use cm configure without sudo, but that breaks the LDAP thing. Anyway if you say don't change it, it proceeds and you can enter the LDAP stuff. I feel like I did all this before, but now it seems to work in cm repo list?!?! So I guess yay, except this was all as clear as mud...