535 results found

1. Prevent closing out of focus semantic merge on escape

   Application will close if you press escape while it's out of focus. This is annoying if you do some back and forth between semantic merge and another application while doing you diff.

   9 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Enable namespaced Labels, display as a tree view

   Just a simple (crazy?) idea. This would be very nice to have when the number of labels in a repo grows large. A hierarchical Labels view would be consistent with the rest of the Plastic UI.

   • Implement "soft" namespacing for labels (i.e "Namespaced Labels/Label 1"), similar to the one for branches.

   • Then add buttons "List view" and "Tree view" to the Labels view, just like the Branches view.

   Technical:
   No change is needed to how label names are stored, but the forward-slash character needs to be allowed in a Label name (it isn't currently, which is great since it means existing Labels won't be namespaced by mistake). The slash should be used to indicate namespace levels. You'd have to accept whitespaces in namespace names but that should not be a problem. Renaming by adding/removing slashes should modify the namespace of the label. Consecutive slashes should be left as-is but treated as a single slash. Namespaces containing only whitespace should be collapsed.

   (NOTE: backslash is currently allowed in a label name, which is a bit odd. If there is a problem with enabling forward-slashes in label names, backslash could be used but that would be less consistent with the rest of the UI.)

   Just a simple (crazy?) idea. This would be very nice to have when the number of labels in a repo grows large. A hierarchical Labels view would be consistent with the rest of the Plastic UI.

   • Implement "soft" namespacing for labels (i.e "Namespaced Labels/Label 1"), similar to the one for branches.

   • Then add buttons "List view" and "Tree view" to the Labels view, just like the Branches view.

   Technical:
   No change is needed to how label names are stored, but the forward-slash character needs to be allowed in a Label name (it isn't currently, which is great since it means… more

   3 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Simple repository clone operation

   When you're working in distributed mode with a local development server and want to join a project, you have a lot of work ahead with PlasticSCM.

   1. Open PlasticSCM, go to repositories view.
   2. Type in the name of your local plastic server.
   3. Create a new empty repository.
   4. Right-Click and create a workspace from that repository.
   5. Open that workspace.
   6. Go to sync replication view.
   7. Add your local repo as source repository.
   8. Add the repository which holds the project you want to join (clone to your local server) as destination repository.
   9. Click refresh.
   10. Pull the changes.
   11. Open your local workspace.
   12. Click update workspace.

   Now compare this to how things are done in git:

   1. git clone git://url.of.other/repo /path/to/local/folder
   2. there is no step 2.

   I think this speaks for itself. The process of cloning a remote repo must be a lot more streamlined.

   When you're working in distributed mode with a local development server and want to join a project, you have a lot of work ahead with PlasticSCM.

   1. Open PlasticSCM, go to repositories view.
   2. Type in the name of your local plastic server.
   3. Create a new empty repository.
   4. Right-Click and create a workspace from that repository.
   5. Open that workspace.
   6. Go to sync replication view.
   7. Add your local repo as source repository.
   8. Add the repository which holds the project you want to join (clone to your local server) as destination repository.
   9. Click refresh.
   10. Pull the changes.
   11. Open your local workspace.
   12. Click update workspace.

   … more

   4 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Exclude identical files from Diff (between selected changesets)

   When selecting two changesets on two different branches and choosing "Diff selected changesets", the resulting Changeset Diff view can contain identical files (files that do not differ at all between the two changesets). This could happen if the same change has been applied to a file on both branches, without a merge.

   In this case I suggest that the identical files be hidden from the Diff view. The whole point of a Diff is to see the files that differ, not the ones that don't.

   (NOTE: In my case, I had loads of identical files due to an import from Subversion via GitSync where some merges were not fully registered as such.)

   When selecting two changesets on two different branches and choosing "Diff selected changesets", the resulting Changeset Diff view can contain identical files (files that do not differ at all between the two changesets). This could happen if the same change has been applied to a file on both branches, without a merge.

   In this case I suggest that the identical files be hidden from the Diff view. The whole point of a Diff is to see the files that differ, not the ones that don't.

   (NOTE: In my case, I had loads of identical files due to an import from… more

   24 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Add Code Review to Macplastic

   I'm not sure how macplastic made it out with a majorly missing feature: code reviews. I'd love if this got some priority.

   9 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. 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 should be done even for "Diff selected changesets".) That way we will see only the items located in the relevant subtree.

   (For symmetry/simplicity, this could be done for the History of a single file as well. That is not necessary though, since it would show the same changes as the inline Diff.)

   For this to be a flexible solution, there should also be added a checkbox next to the "Filter:" box so we can toggle the filter on/off. (That would be a good feature to have, even on its own...)

   The value of this checkbox can be saved to a .conf file. To avoid a change in the default behavior, you can let this checkbox be unchecked initially. Also, when the user manually changes the filter string, you can let this checkbox become checked automatically.

   It would be really super to have this simple auto-populated and toggleable filter, since we often want to review the history of changes done in only a sub-tree!

   NOTE: In TortoiseSVN this feature is activated by the checkbox "Show only affected paths" in the "SVN Show Log" dialog.

   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… more

   3 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Support for CodeLens Change and History

   I'm actually not too sure how this works but it seems like there's an opportunity to provide in-context change history info via CodeLens. I see it with Git changes and it works pretty cool - see attached screenshots.

   ref: http://go.microsoft.com/fwlink/?LinkId=320331

   •  

   •  

   11 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Show progress indication for Undo of many/large files

   When undoing pending changes on a very large (binary) file or a large number of files, the operation can take a considerable amount of time, especially if connecting directly to the repo server over Internet.

   It seems the original file contents are re-downloaded, but that is not directly obvious so a progress indicator (just as for update/switch) would be helpful here. Otherwise one may think that the process has stopped working...

   10 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Improve the conditional format to support to coloring of branches with un-replicated change sets

   I want it to be possible to color branches that have change sets that have not been pushed to some other server via sync replication.

   To be specific and explain the background:
   I use jenkins to do some builds of my project when the main branch has been pushed to a central repository.
   it has happened to me several times that I checked in code (locally) and executed the jenkins project just to discover that it ran old code because my main was not replicated to the main server.

   I would be happy if my main branch would show with some color if it has change sets that have not been replicated to a specific replication server.
   (coloring all the other branches that have not been pushed is also o.k.)

   I want it to be possible to color branches that have change sets that have not been pushed to some other server via sync replication.

   To be specific and explain the background:
   I use jenkins to do some builds of my project when the main branch has been pushed to a central repository.
   it has happened to me several times that I checked in code (locally) and executed the jenkins project just to discover that it ran old code because my main was not replicated to the main server.

   I would be happy if my main branch would show with… more

   6 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Synology NAS drive plugin for PlasticSCM server.

    Create a plastic scm server plugin for Synology NAS to allow the server to be easily hosted on a NAS drive.

    27 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    6 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. 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

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. 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:

    http://plasticscm.uservoice.com/forums/15467-general/suggestions/5125416--save-as-from-browse-repository-on-this-changese

    3 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. 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 repository

    9 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Enable re-merging

    A feature to enable the user to edit/re-merge a pending merge is something that would improve flexibility and greatly assist new users to the system.

    If you accidentally do something wrong in the merge, or change your mind and want to do something differently, it would be great to "redo" either file or the entire merge, and let you change e.g. from workspace to source contributor, or go over a merge of some code without having to undo. Now, after you've done a merge you reach a point of no return.

    1 vote

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    5 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. 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 of view!

    (If switched to a Changeset, this means the same number will be displayed twice but that should not be a problem as long as it's obvious which number is from the selector and which is the actually loaded one. Alternatively, the actually loaded number could be omitted in this case.)

    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… more

    3 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    3 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. 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 incoming merge is part of a changeset that is already displayed. (This should not affect the "Display only relevant changesets" option.)

    Perhaps you could render the incoming end of a merge-arrow and make it "fade away" or become "dotted" further away. Or display a special arrow icon to indicate the non-displayed merge. It would help bring the displayed changesets into context.

    Also, the "View history" and Changesets views could benefit as well from having different icons for each changeset line depending on whether there's an incoming (or outgoing?) merge etc. As it is, the icons in these list views are not really used to their full potential since they are all the same...

    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… more

    3 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    5 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Add button "Set as default workspace path" in New Workspace dialog

    This is a new idea inspired by another uservoice that was declined:
    https://plasticscm.uservoice.com/forums/15467-general/suggestions/10300338-remember-last-entered-path-for-workspace

    However, the solution suggested here supports all three of the conflicting scenarios given by Codice staff when declining the earlier uservoice: a proposed initial default path (set on first install), a configurable root path (now set from GUI) and a way to remember the last entered path (but only on demand).

    There is a setting DefaultWorkspaceRoot in file guiclient.conf, but there is no way to set that from the GUI. I propose adding a link/button "Set as default path for new workspaces" or similar in the New Workspace dialog, next to the workspace path box. When you press that button the mentioned setting should be updated with the currently entered workspace path (minus the filename). That way a user will not have to manually edit this setting in the .conf file, but on the other hand it will not be overwritten if you temporarily use another path for a new workspace.

    NOTE: This feature would be similar to the "Set as default query" used elsewhere in the GUI, so it should be consistent with the overall style...

    This is a new idea inspired by another uservoice that was declined:
    https://plasticscm.uservoice.com/forums/15467-general/suggestions/10300338-remember-last-entered-path-for-workspace

    However, the solution suggested here supports all three of the conflicting scenarios given by Codice staff when declining the earlier uservoice: a proposed initial default path (set on first install), a configurable root path (now set from GUI) and a way to remember the last entered path (but only on demand).

    There is a setting DefaultWorkspaceRoot in file guiclient.conf, but there is no way to set that from the GUI. I propose adding a link/button "Set as default path for new workspaces" or similar in the New… more

    3 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. 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 filters and visibility mode etc should still be applied to the Home branch...

    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… more

    3 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Add option to filter latest N changesets instead of date filter, to avoid empty views

    I'd like an alternative to date filters, so that views will not be empty by default if I look at a branch or a repo that has been is inactive for more than 3 months. I'd rather have a setting "Show 100(+/-) changesets". Sometimes you want to look at a certain time period, but I think more commonly you just want to limit the sheer amount of data being displayed?

    This might need an addition to the "cm find" query language, to specify "the N latest changesets" etc, similar to SQL "SELECT TOP(N) ... ORDER BY ..."?

    Also, an empty Branch Explorer displays "No data found, server did not return any data for specified filter". This indication should be used in all other filtered views too (Changesets, Branches etc).

    I'd like an alternative to date filters, so that views will not be empty by default if I look at a branch or a repo that has been is inactive for more than 3 months. I'd rather have a setting "Show 100(+/-) changesets". Sometimes you want to look at a certain time period, but I think more commonly you just want to limit the sheer amount of data being displayed?

    This might need an addition to the "cm find" query language, to specify "the N latest changesets" etc, similar to SQL "SELECT TOP(N) ... ORDER BY ..."?

    Also, an empty… more

    9 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    3 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Make more views openable by command line flags and Plastic:// URLs

    As mentioned in the following links, the changeset / branch Diff view from the Plastic GUI can be automatically opened to show a specified changeset or branch. This can be done either via command line / script or (on Windows) by a URL containing a special "Plastic://" protocol:

    http://www.plasticscm.net/index.php?/topic/3061-updated-plastic-urls-to-launch-diff-windows/

    http://codicesoftware.blogspot.com/2012/11/plastic-scm-4110372-release-is-out.html

    This is very handy for automation etc. However, I'd like to see more views available via command line and URL args - Branch Explorer, 2D History, Items, Annotate etc...

    53 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating