Settings and activity

  1. 4 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  ·  Flag idea as inappropriate…  ·  Admin →
    Mikael Kalms shared this idea  · 
  2. 42 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  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Mikael Kalms commented  · 

    I'm very much looking forward to this as well.

    We use Plastic to develop Unreal Engine games - and all the art & design assets (and Unreal-specific-metadata files) are binary; we use branches, discipline and coordination to avoid stepping on each others' toes, but travelling locks would make life easier particularly as team & project sizes grow.

    Mikael Kalms supported this idea  · 
  3. 13 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  ·  Flag idea as inappropriate…  ·  Admin →
    Mikael Kalms shared this idea  · 
  4. 50 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  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Mikael Kalms commented  · 

    Personally, I value immutable history highly. I would appreciate an amend feature as long as it does not complicate questions like 'does my colleague have the latest changes from branch X in their current workspace' and 'what was the exact set of input files when build Y was produced'.

    We find that working with per-task branches, it is not a problem to have extra commits for amends. It is when working on a single branch (usually directly on main) that amend operations would be valuable to us. Therefore, we try to use task branches as much as possible.

  5. 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  ·  Flag idea as inappropriate…  ·  Admin →
    Mikael Kalms shared this idea  · 
  6. 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  ·  Flag idea as inappropriate…  ·  Admin →
    Mikael Kalms shared this idea  · 
  7. 36 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  ·  Flag idea as inappropriate…  ·  Admin →
    Mikael Kalms supported this idea  · 
  8. 82 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  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Mikael Kalms commented  · 

    Seconded. I performed an incorrect check-in just now, and ended up on this page when I was looking for a way to undo the check-in and split it into multiple smaller check-ins.

    Being able to undo the results that clicking the Check-In button produced (a new changeset created on a branch) is effectively one way of rewriting check-ins.

    I suspect that this gets a lot more complicated when considering A) can this be done against Plastic Cloud as well as a local server? B) what about if the changeset already has been replicated? and C) what about information that was not stored with the changeset, like, which was the list of files that were locked, but got unlocked by the Check-In operation? and I do not have good ideas on a design that handles those problem areas. (For example, Git docs say 'don't rewrite history for changesets that already have been replicated' but it has no warnings / no protection for this.)

    Mikael Kalms supported 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  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Mikael Kalms commented  · 

    You can experience this -- sort-of -- since client version 6.0.16.884; if you have the Plastic SCM main window open on part of your screen, and open one diff window on another part of your screen, then the diff window's contents will change when you move around in the Branch Explorer. It is not as convenient as having it integrated into the main window though.

    http://www.plasticscm.net/index.php?/topic/20268-automatically-show-list-of-affected-files-in-a-changeset-when-navigating-in-branch-explorer/ contains an example mock-up of what it could look like with a docked list of files (but not an exact list of changes).

    Mikael Kalms supported this idea  · 
  10. 6 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  ·  Flag idea as inappropriate…  ·  Admin →
    Mikael Kalms shared this idea  ·