Skip to content

Settings and activity

133 results found

  1. 87 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Göran Wallgren supported this idea  · 
  2. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Göran Wallgren commented  · 
    An error occurred while saving the comment
    Göran Wallgren commented  · 

    This also goes for the "pending changes" changeset (-1) which is currently not displayed in a 2D revtree, not even if it there are changes in the selected file!

    Also, I'd like to see a "pending changes" changeset as soon as there are local changes in source-controlled items, even though no item is checked-out. That would make more sense in the simplified modify-checkin workflow...

    Göran Wallgren shared this idea  · 
  3. 12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Göran Wallgren supported this idea  · 
  4. 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  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Göran Wallgren shared this idea  · 
  5. 9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Göran Wallgren shared this idea  · 
  6. 33 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Göran Wallgren commented  · 

    This is an excellent idea, useful not only for correcting mistakes. Only being able to shelve pending changes is limiting, you might want to shelve a change but forget to do it before Checkin. Even worse, you may plan to press Shelve (by expanding the Checkin button) but by accident or "A Momentary Lapse of Reason" you press the Checkin button instead. Then you can't shelve...

    This could serve as a lightweight implementation of this request:
    https://plasticscm.uservoice.com/forums/15467-general/suggestions/3742293-move-changesets-to-different-branch

    One potential problem here (when used to correct a mistaken Checkin) is the fact that when you shelve a changeset, the shelve has a dependency on the changeset it's based upon. This currently makes it impossible to delete that changeset, even if there are no other dependencies. Would it be possible to (optionally?) break this shelve-dependency and have the shelve behave like a pure "patch diff"?

    Göran Wallgren supported this idea  · 
  7. 13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Göran Wallgren supported this idea  · 
  8. 53 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Göran Wallgren shared this idea  · 
  9. 9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Göran Wallgren commented  · 

    Hi robl, not sure if this is what you were seeing but I got hundreds of "U" changesets in 2D History Tree by accidentally unchecking "Display only relevant changesets" which is linked to the slightly hidden settings under the "Version tree" vertical tab inside the "Options" sidebar in 2D History Tree. This is in v5.4.16.

    Göran Wallgren supported this idea  · 
  10. 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  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Göran Wallgren commented  · 
    Göran Wallgren shared this idea  · 
  11. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Göran Wallgren shared this idea  · 
  12. 4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Göran Wallgren commented  · 

    No. This would not make listing slower, since any data that is slow to read-out can be put in the sidebar, meaning that you can defer the read-out until you select one of the repos and then you need only read from the selected repo. (If needed, cache the info and add a Refresh icon in the sidebar Properties tab for manual re-read...)

    An error occurred while saving the comment
    Göran Wallgren commented  · 

    Latest changeset-number, date-time of latest changeset...

    An error occurred while saving the comment
    Göran Wallgren commented  · 

    Motivation for this is of course to be able to quickly find more info about the repos. (Size, age, complexity...) As it is, I can't tell large repos from small or empty ones etc, without opening further views.

    (BTW, the repid is useful for DB maintenance.)

    An error occurred while saving the comment
    Göran Wallgren commented  · 

    More things to report in the sidebar "Properties":
    * Object count (like in the replication/sync summary report).
    * Number of revisions?
    * repid
    * repguid

    Göran Wallgren shared this idea  · 
  13. 7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Göran Wallgren commented  · 

    Not entirely, as "Update workspace" will not bring you to the latest changeset on the branch.

    For this reason, I recommend my coworkers to always switch to branch (unless they are to build from an old changeset).

    Having both commands available on a changeset would IMHO be convenient and logical:
    "I want to switch to the branch where this changeset resides".

    Göran Wallgren shared this idea  · 
  14. 5 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  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Göran Wallgren shared this idea  · 
  15. 2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Göran Wallgren shared this idea  · 
  16. 31 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Göran Wallgren supported this idea  · 
  17. 5 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  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Göran Wallgren commented  · 

    I'd also want a very quick way to extend the date-filter to cover more of the truncated branch. (Most often it will be truncated in the older end...)

    Göran Wallgren shared this idea  · 
  18. 105 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Göran Wallgren supported this idea  · 
  19. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Göran Wallgren shared this idea  · 
  20. 24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Göran Wallgren commented  · 

    I agree. For a pending merge changelist, indicate which files had manual conflict edits applied so you can re-check your conflict resolution before checkin (without being cluttered by fully-auto-resolved files).

    Göran Wallgren supported this idea  ·