Settings and activity
19 results found
-
1 vote
An error occurred while saving the comment An error occurred while saving the comment psantosl commentedHi Johan,
Yes, understood. Just to make it crystal clear:
* You ALREADY merged a file.
* But you need an option in Pending Changes that says "restart merge for this file" -
3 votes
An error occurred while saving the comment psantosl commentedHi Steven,
Sounds like a good idea.
How do you see this?? I mean, some sort of "create repo using template" that immediately setups some branch names??
-
4 votes
An error occurred while saving the comment psantosl commentedAre you aware of any scripts available to merge this?? If so, it would take us minutes to get it integrated.
-
46 votes
An error occurred while saving the comment psantosl commentedHi,
Are you using the latest 5.0 release?? Have you seen the improvements to item merge tracking there?
http://codicesoftware.blogspot.com/2013/11/plastic-scm-release-5044505-including.html
I think this fixes the issues you mention, correct?
-
68 votes
An error occurred while saving the comment psantosl commentedAre you using C#? If so, why don't you take a look at "method history"?
-
44 votes
An error occurred while saving the comment psantosl commentedNice one! Looks a little bit difficult but doable! :)
-
15 votes
An error occurred while saving the comment psantosl commentedWe hope to have it working in a few days... but not there yet! :(
An error occurred while saving the comment psantosl commentedYes Ignacio, please keep in mind the "known restrictions" we sent to all alpha testers :)
"* The plastic repository can be only synchronized with a single git
repository. It means, it will only receive/push changes from/to git.
This mapping cannot be changed. (It is totally temporary, we'll overcome
this soon)" -
2 votes
An error occurred while saving the comment psantosl commentedDoes shelve help?
An error occurred while saving the comment psantosl commentedDoes shelve help?
psantosl supported this idea · -
23 votes
An error occurred while saving the comment psantosl commentedWe've some questions about this one after talking about it. Would you mind contacting us to discuss?
An error occurred while saving the comment psantosl commentedIt is so cool that we're going to get it done... :) We're still considering some pros and cons, but I talked to the team today and we all agree it will be a cool poster feature :)
-
5 votes
An error occurred while saving the comment psantosl commentedDo you mean adding a way to download content from SVN or git?
We're about to release the beta of "bisync" which let's you push and pull from plastic to git (github, bitbucket, whatever...). I think it will be helpful too!
-
0 votes
An error occurred while saving the comment psantosl commentedDo you mean repositories or workspaces?
If workspaces: to create a wk, you've to get access to the remote client machine (not server) which I think is a little bit off-topic, isn't it?
-
11 votes
An error occurred while saving the comment psantosl commentedYes, this would be awesome... Certainly something to look at.
Any preferred user system? Facebook? google? Anyone?
-
93 votes
An error occurred while saving the comment psantosl commentedHi Alex,
Well, it is a nice idea. This way when you look into file history you can see how a file was split into two or more...
It is not the first time we consider it. Old SVN had it too (some option in the copy command).
I'm thinking about how to implement it: maybe some sort of:
cm split foo.c foo-partial.c that simply links the two files or something similar.
Then some sort of special link between the revisions so that history can follow the links and so on... would it be fine? All including some sort of cool GUI :)
Maybe instead of cm split, some sort of "cm link" to add a "history link" between two revisions... what do you think? Sounds lower level but doable too :)
-
0 votes
An error occurred while saving the comment psantosl commentedWe'll be readding this feature... got "lost in translation" while moving from 3.0 to 4.0 (on purpose)
An error occurred while saving the comment psantosl commentedIn fact we've the command, but we need to renew it to get it back up and running on 4.0.
Anyway, are the inconsistencies something common? They shouldn't! -
3 votes
An error occurred while saving the comment psantosl commentedWe'll review it early next week.
-
13 votes
An error occurred while saving the comment psantosl commentedSo Lane, which features do you have exactly in mind? Can you share them with us?
An error occurred while saving the comment psantosl commentedYes! We definitely need to improve the Eclipse part! :)
-
50 votes
An error occurred while saving the comment psantosl commentedSoren,
You've multiple selection. You can create a single sync view with several sources and targets. Then do a multi-selection, then push or pull.
An error occurred while saving the comment psantosl commentedNot exactly the whole thing... but most of it is here! http://codicesoftware.blogspot.com/2012/02/after-accidentally-cloning-sexy.html
-
1 vote
An error occurred while saving the comment psantosl commentedWhen you add a new tree, you add a new changeset because if you've the right options configured (which I personally don't like much) it gets checked-in directly.
-
65 votes
Plastic SCM 10.0.16.5668
https://www.plasticscm.com/download/releasenotes/10.0.16.5668Windows – Plastic: Auto-update!
Now you can update Plastic on Windows to the latest version from within the application itself.
When Plastic detects that a new version is available, the help panel will display a notification telling you which version is available. On the help panel is a link to download the latest version.
An error occurred while saving the comment psantosl commentedWe can use the blog so you'll see it in the "RSS" panel.
But yes, we can add an specific icon telling you there's a new version. The only "issue" is that you need to get the server upgraded (sometimes) so... But ok, we'll figure out something.
Hi again Johan,
There are a few special cases to handle:
* What if the file was changed on the workspace prior to the merge you want to redo? (Whether manually modified or as a result of a previous merge?). Should we go back to the previous content? It is far from trivial in most cases.