Good point.

We've a few major changes at hand right now, but we'll get back to this to see what we can do.

Well, I don't consider it a bug but a pending feature, because it is not failing, it simply isn't there :-) (I mean, unless sync with SVN is also a bug :P).

Yes, this is a must... As soon as we finish a few open projects we have in the works, we'll work on this one. In fact I'm eager to get this done... it has been supported since Vista at least and we never took advantage of it.

pablo

Yes, not a bad point.

I don't specially love it because it means making the menu even bigger, which I don't like but...

Hi Jan,

I don't see the F5 issue, but I see you switch to the newly created wk and the items view (is this what you mean by "workspace overview"?) is not shown.

What do you mean by update it? Download to disk?

Yes, it is a good idea and in fact it is not a new one.

The only reason why we didn't do it yet is because it means breaking compatibility between client and server because it means adding a new field, so we're delaying it to group it with more changes once we break 5.4.16 (16 is the compat number) compatibility.

In https://www.plasticscm.com/download/releasenotes/5.4.16.656 we released the option to group repostories.

You're right and in fact we've a bunch of notes referring to how to improve it. It is on the top of the list now.

Do you know you can use another client.conf to achieve this?

Why don't you just start two different Plastic clients?? And move each of them to a different window?

Do you mean label colors in branch explorer, correct?

Hey!

While it is certainly a good idea, I wonder if it shouldn't be implemented through scripting. Thoughts?

Hi,

I guess you mean the one on the left, since the one on the right is typically the working copy, correct?

A slider is a good option for a linear history, but not valid for branches (not very comfortable) which is what you tend to use with Plastic.

The idea is good, but we have to find a way to make it happen.

Any additional ideas would be great.

This is actually something we have on the roadmap but has been postponed several times. It is not trivial but neither very difficult to do.

What we have in mind is to have something like: split repo A into different subrepos, creating new ones.

Yes, you're right. We have to work on a major rewrite of the code review system, adding extra features, making it more usable... and supporting the review of xlinked revisions :-S

Are you using the latest versions of 5.4 and 5.0? Because now you can drag from Plastic to the explorer.

But what you're pointing is different, isn't it? You would like to add a file to the pending changes view?? Please clarify

Hi Robl,

Do you know why we show the "U" marked revisions, correct?

The thing is that the merges happen between changesets, not between revisions, and hence you can be merging changeset 104 which contains a revision from file 'foo.c' which was created in cset 100, and then 101, 102, 103 and 104 are marked with a "U" because the file wasn't modified there, but the merge happens between 104 and the destination cset. Is that clear?

Sorry but I don't understand what you mean? Would you mind explaining what you mean about the icons?? We don't check in the file icons. Just display them from the OS.

In order to automatically push, why don't you just write an after-checkin trigger??

We never started this one so far.

At the end of the day we always end up using CmdRunner and a couple of commands to get this one solved, although doing it from the CLI makes sense.

We'll do our best to push it forward.