Settings and activity
191 results found
-
6 votes
An error occurred while saving the comment -
1 vote
An error occurred while saving the comment Yes, I can tell you some users will find this extremely annoying. We just got an entry in StackOverflow complaining about how disgusting the confirmation after clicking "switch to branch" is. :-O
While I really appreciate this suggestions, please keep in mind this small points tend to be time consuming and steal time from creating big features, the ones that you can explain when someone asks "why is plastic better than X"?
Thanks,
pablo
-
12 votes
An error occurred while saving the comment Loved the idea!
Let's see when we can implement it :)
-
5 votes
An error occurred while saving the comment It should only work if the webui is configured... uhm... maybe we should add some sort of custom field so that users can build extra info to pass to the issue tracker somehow.
Other option is to write your own extension: https://www.plasticscm.com/documentation/extensions/plastic-scm-version-control-task-and-issue-tracking-guide.shtml#WritingPlasticSCMcustomextensions and then be able to tweak it as you need :-)
-
13 votes
An error occurred while saving the comment Hi Soho,
Creating branches from tickets already there! :-)
An error occurred while saving the comment All good ideas.
While most of us prefer a branching convention, definitely creating a branch from a list of tickets looks like the way to go.
-
4 votes
An error occurred while saving the comment Hi!
Would it be possible to merge them using Altova's XML merge tools? If so, automating the merge would be a matter of just a couple of scripts...
-
6 votes
An error occurred while saving the comment Not yet there, but hope you enjoyed this: http://codicesoftware.blogspot.com/2015/08/track-refactored-code-across-files-with.html
-
6 votes
An error occurred while saving the comment 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.
-
114 votes
An error occurred while saving the comment 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).
An error occurred while saving the comment 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
-
4 votes
An error occurred while saving the comment 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...
-
1 vote
An error occurred while saving the comment 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?
-
15 votes
An error occurred while saving the comment 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.
-
27 votes
An error occurred while saving the comment In https://www.plasticscm.com/download/releasenotes/5.4.16.656 we released the option to group repostories.
-
59 votes
An error occurred while saving the comment 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.
-
9 votes
An error occurred while saving the comment Do you know you can use another client.conf to achieve this?
-
3 votes
An error occurred while saving the comment Why don't you just start two different Plastic clients?? And move each of them to a different window?
-
7 votes
An error occurred while saving the comment Do you mean label colors in branch explorer, correct?
-
9 votes
An error occurred while saving the comment Hey!
While it is certainly a good idea, I wonder if it shouldn't be implemented through scripting. Thoughts?
-
6 votes
An error occurred while saving the comment 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.
-
13 votes
An error occurred while saving the comment 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.
We've just fixed this for Linux, where it was an issue for some releases.
Will this get the problem fixed?
Thanks,
pablo