Skip to content

General

General

Categories

JUMP TO ANOTHER FORUM

307 results found

  1. Powershell is growing and Windows is ensuring that admin will eventually learn Powershell (sort of Object-Oriented-Shell in Windows)

    It might be wise to prepare for providing powershell-native modules as midterm strategy.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. When you try to save a modified in memory read-only file in VS with PlasticSCM set as current version control plugin, VS will show you a Save As dialog instead of asking you to overwrite file or discard your changes as it normally does (without PlasticSCM plugin).

    More details here:
    http://www.plasticscm.net/index.php?/topic/2257-unable-to-overwrite-read-only-files-with-plasticscm-in-vs2013/

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. First double click on a comment in a Code review tool takes you to the file containing the commented line and only the second double click takes you to the commented line. I don’t see the reason for such behavior; it is irritating actually. It would be nice, if the first double click takes you directly to the commented line without the need to switch to that file in a separated step.

    47 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. At least the simple one as it is in an internal diff. However, it should be enabled by default (and/or remember that I enabled it). It would be even better if it was able to use the syntax highlighting automatically according to a file extension.

    41 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Sometimes it would be useful to pick out a file in an old revision. What I want is to go to Browse repository on this changeset, select a file, click on Save as (in a context menu), find a destination on a filesystem and save a copy of that file there.

    29 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Automatic merge fails in the following situation:

    For a particular source code line on separate branches:

    1) add a new line before or after it
    2) modify the line

    When rebasing one of the branches from the other this fails, apparently because the new line is grouped with the other in the diff tool. If they were considered separately it should be a trivial automatic merge.

    An alternative would be to make the manual resolution easier by providing a mechanism to split the merge block so each line can be selected separately (source/base/dest). I think xxdiff has this capability. Currently…

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. The custom Open with context menu (as it is in an Items view now) would be useful in Diff changeset too.

    27 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Sometimes when you modify a file and then rename it, Plastic SCM is unable to match the original file with the renamed one. In that case you can use the ‘Search matches’ tool to select the file that matches the original one. However, It is not always possible, because the minimum similarity level that you can set when searching is 50%.

    Imagine you add a comment to a small file that contains only a definition of an enumerable and then rename the file. Because it is small, the comment becomes a major part of the file and the similarity to…

    28 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hello,

    we have changed the Search Matches form to remove the minimum similarity level. Moreover, we have changed the matching algorithm so that changes in indentation are not taken into account.

    These new features can be found since version 5.0.44.566 of PlasticSCM.

  9. As used in SemanticMerge the build in Text Merge tool does not have keyboard shortcuts. This makes it frustrating when you can use hotkeys for SemanticMerge but not for the external tool provided with SemanticMerge.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    In the current version of PlasticSCM, the merge tool has the following shortcuts:

    • Select/Unselect source: Ctrl+1
    • Select/Unselect base: Ctrl+2
    • Select/Unselect destination: Ctrl+3
    • First conflict: Ctrl + Shift + -
    • First conflict: Ctrl + -
    • Next conflict: Ctrl + +
    • Last conflict: Ctrl + Shift + +
    • Previous non-automatic conflict: Ctrl+PageUp
    • Next non-automatic conflict: Ctrl+PageDown
  10. High DPI support for high resolution/ high DPI workspaces. Than you!

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. When listing changed files in a cs or pending changes, optionally list the number of lines changed in each file in the table. This would help in finding the important files from a large number of files.

    Difficulties finding a revision to compare to make this hard to script from the command line.

    It probably should ignore whitespace.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Sometimes when a file is moved or renamed the pending changes view doesn't track this change as move operation, but as delete and add. It would be great if the user could tell plastic that this should be handled as a move.

    You may add such an option to the context menu while one deleted and one added file are selected. It's your choise.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. There are only changeset numbers and base/source/destination titles shown in the Merge Tool (or any external merge tool). It will be very helpful if the names of branches will be shown too. When I merge one branch to another I do not remember (and care about) the changesets numbers and I might be not confident what the source is and what the destination is. The branch names would help me to figure out which version is which immediately.

    14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. When diffing revisions set the revision from the older changeset as a source and the revision from the newer changeset as a destination independently on the revision sorting in the History view.

    29 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. I think it will be more consistent to highlight (with a darker color) all added characters, even on lines which are all new. See the picture:
    http://s15.postimg.org/uln6ryq17/diff.png
    Otherwise it is more difficult to distinguish what was really changed. Especially for longer lines.

    81 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. It would be awesome if I could filter the Branch Explorer in the same manner as the Changeset view (simple filter and custom find command). The filtered out changesets will be hidden as they are when using Show only relevant changesets or History of an item as a 2D tree.

    19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. I would recommend you provide instructions for:

    Meld,Beyond Compare, DiffMerge, KDiff3 but I will leave you to determine and others to determine what is appropriate.

    Atlassian SourceTree has build in options for:
    AraxisMerge, Beyond Compare, DiffMerge, KDiff3, P4Merge, TortoiseMerge

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. You missed including SCCS in your history. It dates back to 1972.

    http://en.m.wikipedia.org/wiki/Source_Code_Control_System

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Currently, (in "centralized mode") if a server cannot be contacted, the plastic client GUI won't open, even if there are multiple profiles, and another server IS contactable. This appears to depend on the last active workspace - if the last active workspace belongs to the server that is down, the tool can't be opened.

    It would be extremely beneficial to be able to open the tool, and select a different workspace weather the current server is available or not - perhaps show those workspace(s) as greyed out or non-available, disable or close the tabs

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. This command fails if any of the items already exist. It would be more useful if it just ignored existing items. Typically I would run it on a subdirectory of my workspace.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    It has been included on release 5.4.16.704:
    Command Line Interface: The cm add and the cm partial add (gluon CLI) commands now accept a new parameter: —ignorefailed. This new parameter allows to skip items that cannot be added without rejecting the whole add operation.
    REMARK: If a directory cannot be added, none of its inner items will be added either.

1 2 6 8 10 15 16
  • Don't see your idea?