526 results found
-
option to cancel workspace update
A workspace update can be quite slow, particularly if you made a mistake in cloaked.conf. Rather than killing the process, it would be nice to be able to cancel the update.
22 votes -
Add "unrelated merge" indicator in 2D history and filtered branch explorer
When viewing changeset history I tend to think about changesets in terms like "that is the checkin where I merged/rebased from /other_branch". That kind of context is sometimes lost in the Plastic views:
In 2D History if a merge is unrelated to the selected item then the merge arrow is not displayed.
In Branch Explorer if the /other_branch is hidden by filter, the merge arrow is not displayed.
Not displaying the merge arrow in these cases is logical since the /other_branch is unrelated or hidden. However, I'd find it helpful to have some kind of (optional) visual indicator that an…
3 votes -
If a changeset is deleted, switch to the parent changeset and KEEP the changes in the "pending changes"
When a changeset is removed the workspace is switching to the parent changeset and all changes get lost.
I think it is better to keep all changes in the "pending changes", so you do not lose any changes and you can add some more changes.It often happens to me that I forget some small changes, so I have to check in again producing a lot of unnecessary changesets.
87 votes -
Add default filter in Changeset Diff opened from (2D) History
This suggestion is a simple and minimal solution to a feature that is missing in Plastic and that we used a lot in TortoiseSVN - the ability to filter a Changeset Diff to the subtree-path that we're viewing the History of.
I have earlier suggested more elaborate changes to support this feature, but the simplest possible fix for this is as follows:
When opening a Changeset Diff from a (2D) History view of a directory (subtree), automatically populate the "Filter:" box (for the Changeset Diff) with the workspace path of the directory that the History view is working against. (This…
3 votes -
Display more information in the Repositories view
In the Repositories view, very little information is displayed about the repositories listed: Name, namespace/hierarchy, server. That's all.
When I list my repositories I want to see something similar to the Branches view: Owner, Creation date, Comment
(The Comment field was requested in another uservoice: https://plasticscm.uservoice.com/forums/15467-general/suggestions/8063376-repository-description)
But most importantly, I'd like to see number of branches, number of labels, number of changesets! This info could be displayed in an "extended information" sidebar, also just like in the Branches view.
4 votes -
Search in Branch Explorer should include Branch Comments
The filter box in the Branches view gets hits on words in the branch comments, but the Search box in Branch Explorer does not.
6 votes -
Extend "Explore changesets on branch" to new command "Explore history" in Items view
When looking at a branch, we find the "Explore changesets on this branch" window to be very useful, more so than the similar "View changesets on this branch".
In the Items view, the command "View history" is similar to "View changesets on this branch" but it is further filtered to cover only the selected subtree or single file. However, there is no equivalent to the "Explore changesets on this branch" window for the Items view.
I propose adding a context command "Explore history" in the Items view, so that the excellent "Explore" window can be similarly filtered to a subtree…
4 votes -
Possibility to merge independently added files/directories
Two folders (or files) with the same name added into different branches independently, cannot be merged in Plastic now.
It would be priceless in some cases (especially for folders).
http://www.plasticscm.net/index.php?/topic/1224-evil-twin-conflict-resolution/
http://www.plasticscm.net/index.php?/topic/391-directory-merge-fail/175 votes -
Lock a Branch
LOCK a branch so no one can perform a merge or checkin except the one who took the lock.
Current scenario: Two or more developers are are working on child branches and want to merge back to the parent branch, if both initiate the merge, the first will succeed but the second will have to re-merge again. To avoid this, the developers can send an email, asking all to wait until he finishes the merge...
Proposed solution: Allow the one to take a lock on the target branch, do the work, and release it. During the lock, others should be…102 votes -
Show current changeset in "selector bar" (below workspace tab)
When starting the Plastic GUI (on Windows), the tab for the active workspace tab is selected. Below that is a "selector bar" indicating what's currently loaded (switched to) in this workspace.
If the workspace is switched to a Branch/Label, there is no immediate way to find out which changeset number is actually loaded right now.
Example: When switched to a branch, if the workspace has not been Updated recently we may not be at the latest changeset on that branch.
I propose displaying the actually loaded changeset number in this "selector bar", to have this crucial information readily available regardless…
3 votes -
conditional format/in-/exclusion rules based on repository
Right now I have no way to define custom rules for only one repository.
Also it is not possible to identify the repository within the rules condition.Workaround: add a attribute to each branch containing the repository name. (Very very nasty)
It would be nice to:
1) have a repostoryName variable within conditions
2) have custom rules for only one repository9 votes -
MergeTo operation shall support --mergetype and -c/-commentsfile
It looks that currently MergeTo operation is ignoring --mergetype parameter. If only automatic merge of changes from both source and destination is possible Plastic is doing it.
It would be good to have a chance to explicitly show that changes only on one side are allowed and exit with failure if there are some also at the other.
Additionaly for now it is not possible to give comment which will be used for check-in operation after successful mergeTo.
6 votesOn the release 7.0.16.2077, we added the new server-side merge that extends the existing merge-to functionality.
Using the server-side merge, the file conflicts can be resolved and the merge resolution options (—mergetype, —keepsource & —keepdestination) are supported.
The server-side merge is still on preview so you need to enable it adding the following setting on the client.conf. Check how to do it on the release notes: https://www.plasticscm.com/download/releasenotes/7.0.16.2077
Remarks, the server and client version must be equal or newer than 7.0.16.2077 to use the server-side merge.
We comment option will be documented soon, we already plan a task to do it in the next few weeks. Sorry for the delay.
Best regards
Borja
-
Make Diff listen to file-change-notifications and ask to reload
The Diff view/window in Plastic does not listen to filesystem notifications about file-changes when diffing a file in a workspace.
It should discover external changes to the workspace file and ask to reload/recalculate the diff when needed. Other Diff tools I have tried do this...
6 votes -
Show Home changeset whenever possible
I would like the "Home" changeset to always be shown (when at all possible) in all the branch-explorer/2D-revtree views. This would make it easier to relate the view to the current workspace contents.
In all those views, I'd like the Home changeset to be displayed regardless of date filter (possibly with a dotted parent-changeset arrow to connect it with the nearest date-filter-included changeset).
In the 2D revtree I simply want an extra U = Unchanged changeset (on the relevant branch) with the Home icon above it, in the cases where the home changeset/branch would not otherwise be included.
NOTE: Exclusion…
3 votes -
Add "Switch workspace to this branch" to context menu for changeset
Switching to a changeset is something you rarely do, compared to switching to a branch which is a very common operation. It would therefore be very convenient to have the latter command available even when a changeset is selected (in the Branch Explorer).
When switching to a changeset, the workspace is pinned to that changeset and can not be updated. This was confusing for us when we had just migrated to Plastic, and we still have users doing the mistake of switching to a changeset instead of a branch. I think having both variants of the Switch command available when…
7 votes -
Change the wizards and profile creation to allow working mode and credentials to be changed/overridden
You used to be able to specify the working mode and credentials (username & password) when configuring the client and creating profiles. Now, if the server is set to ADWorkingMode it forces the client to also use ADWorkingMode and forces th userid & password to the local domains credentials. This makes connecting to plastic server from remote locations problematic and rather difficult to achieve. If you could still simply change the client to LDAPWorkingMode and profile username/password it would be much easier to accomplish this.
6 votes -
Add "Open" and "Save this revision as" in 2D (File) History as well
In the Items view, for a single file we have the (customizable) submenu "Open".
In the History list for a single file, we have the "Save this revision as..." command along with "Open" and "Open with...".
For consistency and ease-of-use, the "Open" submenu should be available in the 2D History view for a single file as well. Also, the "Save this revision as..." command should be added to this "Open" submenu.
This is much related to another uservoice that requests adding the "Save this revision as..." command to the "Open" submenu in the Items view as well:
3 votes -
VS plugin: Add in-editor diff markers with associated commands
We were using the VisualSVN plugin for Visual Studio before, and we miss the excellent "Quick Diff" feature: https://www.visualsvn.com/visualsvn/features/
This feature replaces/enhances the "Track Changes" markers in the Visual Studio code editor with colored lines (in the left margin), to indicate blocks of lines that are changed relative to the latest changeset (different colors for modified, added, deleted). It also adds commands (revert block, navigate prev/next change block).
There are some other (open source) plugins that offer similar functionality: "Git Diff Margin", "TfsPendingChangesMargin", "HgVS".
12 votes -
Allow setting a color for each label, changeset and branch
It would be a nice feature to allow setting a color for elements.
Examples:
- set the label color red to mark it as "important".
- set the branch color to green to indicate that the branch is the "test branch"46 votes -
option to select diff tool on the command line
If you use a console based diff tool such as vimdiff it can cause the GUI problems. It would be nice to be able to set different difftool preferences for the GUI and 'cm diff', possibly with a command line option:
cm diff --tool=vimdiff
It might be necessary to give tools names or id's in the GUI preferences to reference from the command line so you can easily configure the arguments.
9 votes
- Don't see your idea?