AdminCodice Software
(CEO / Founder, plasticscm)
My feedback
-
9 votes
-
3 votes
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.
-
11 votes
In order to automatically push, why don't you just write an after-checkin trigger??
-
47 votes
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.
-
20 votes
Thanks SWSBB! :-)
It looks like a good idea. It won't take long to code.
-
9 votes
Do you know you can pay with your credit card without having to create any sort of paypal account??
-
3 votes
Thanks for the detailed explanation Gerard.
-
72 votes
Hi Volker,
can you please tell me which Plastic SCM version are you using?
If I'm working in the changeset number 18 and I delete it my workspace will be automatically updated to the 17. Of course the changes done in the 18th will be lost.
If you want to preserve the changes done in the 18th we can think about it and it would be another idea but first lets make sure that the workspace is at least updating you to the parent changeset.
We need more information about this idea.
1) I can't reproduce the behavior about the fact you said about "and all changes get lost". Can you please give us more info?
2) "Switching to the parent changeset..." I guess that you are switching with changed items (blue tick) and not with checked out items right?Correct me if I'm wrong but is what you want the following?
You have the csets 15, 16, 17 and 18.
You want to be able to remove the cset 18 and preserve the changes done in that changesets inside the Pending changes view?
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?