Settings and activity

  1. 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  ·  Flag idea as inappropriate…  ·  Admin →
    Max Pixel 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…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Max Pixel shared this idea  · 
  3. 5 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
    Max Pixel commented  · 

    This would be very useful for document repositories. Currently, I have several single-file repositories, one for each document that should be branchable/instantiatable, which ends up being a bit kludgey (but still better than no version control or branching at all).

    repos:
    documents
    documents/contracts (empty)
    documents/contracts/MNDA
    documents/contracts/vendor

    file tree:
    contracts/
    ____MNDA/ (xlink to main@contracts/MNDA)
    ________MNDA.docx
    ____vendor/ (xlink to main@contracts/vendor)
    ________vendor contract.docx
    client/Contoso/
    ____vendor contract for superapp/ (xlink to Contoso@contracts/vendor)
    ________vendor contract with Contoso for superapp.docx
    ____MNDA/ (xlink to Contoso@contracts/MNDA)
    ________MNDA with Contoso.docx

    There are a lot of unnecessary folders for single files. If I could xlink a single file, it would be a lot cleaner, and I could have just a single repository for the templates.

    Repos:
    documents
    documents/instantiatable

    contracts/
    ____vendor contract.docx (xlink to main@instantiatable)
    ____MNDA.docx (xlink to main@instantiatable)
    client/Contoso/
    ____vendor contract with Contoso for superapp.docx (xlink to Contoso@instantiatable)
    ____MNDA with Contoso.docx (xlink to Contoso@instantiatable)

    Max Pixel supported this idea  · 
  4. 7 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 →
    Max Pixel supported this idea  · 
  5. 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  ·  Flag idea as inappropriate…  ·  Admin →
    Max Pixel shared this idea  · 
  6. 10 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 →
    Max Pixel supported this idea  · 
  7. 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  ·  Flag idea as inappropriate…  ·  Admin →
    Max Pixel shared this idea  · 
  8. 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  ·  Flag idea as inappropriate…  ·  Admin →
    Max Pixel shared this idea  · 
  9. 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 →
    An error occurred while saving the comment
    Max Pixel commented  · 

    This would greatly facilitate Plastic's advocated practice of making task-branches with changesets crafted to tell the story of the task's development.

    Max Pixel supported this idea  · 
  10. 46 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 →
    Max Pixel supported 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  ·  Flag idea as inappropriate…  ·  Admin →
    Max Pixel shared this idea  · 
  12. 50 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  4 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Max Pixel supported this idea  · 
  13. 94 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 →
    Max Pixel supported this idea  · 
  14. 116 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 →
    Max Pixel supported this idea  · 
  15. 1 vote
    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 →
    Max Pixel shared this idea  · 
  16. 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 →
    Max Pixel shared this idea  · 
  17. 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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Max Pixel commented  · 

    While you're at it, might as well do the same for `cm unlock`. If I `cm unlock 168ffbb4-ef54-4ee4-af4d-0dfd97050b1b`, and that GUID exists in the repository `assets`, and `lock.conf` contains `rep:assets lockserver:ServerA:8084`, then I expect it to actually do something. Instead, it does nothing, because nothing is locked on my local server. I am required to run `cm unlock ServerA:8084 168ffbb4-ef54-4ee4-af4d-0dfd97050b1b`

    Max Pixel supported this idea  · 
  18. 59 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Max Pixel commented  · 

    I've discovered another sour aspect of this dysfunction: Merging.

    Scenario:
    Artist changes "Foo" on "art" branch, checks it in alongside "Bar"
    Artist gets feedback and starts modifying "Foo" again, checking it out
    Developer needs "Bar" in order to do their work, so they try to merge from "art" to "dev"
    But it doesn't work - the merge contains a revision to "Foo", and "Foo" is currently checked out, so the merge fails.

    The merge shouldn't fail, because it's not actually creating a new revision of "Foo" - it's carrying over an older version. Plastic has no reason to think that "Foo" will be modified as a part of the merge, because it's "changed on source only, no conflict".

    My team runs into this every other day. It happens increasingly often as we move from "building new features" to "revising existing features" - a situation where, ironically, exclusive checkout is even more important. In order for developers to not be completely blocked by checkouts that have no logical reason for blocking their needed merge, we need to either check-in prematurely, or shelve changes (in the case of Gluon users, this means copy to desktop, then unco, then move back from desktop after coworker has finished merging).

    It's a major waste of time, and we're starting to question if maybe it's a bigger waste of time than running into conflicts, or doing exclusive checkout manually through something like a Google Doc of "who has what".

    Max Pixel supported this idea  · 
    An error occurred while saving the comment
    Max Pixel commented  · 

    I'm in strong support of this. This highlights a serious flaw that objectively cripples the lock system. I hope that the misinterpretations in the comments don't hurt the chances of this becoming a feature. I'll try to clarify even more. This is even more important for UE4 where Blueprints are even less mergeable than Unity assets.

    The way it currently works:
    1. Alice checks out Foo.uasset on branch main/A
    2. Bob cannot check out Foo.uasset because it is locked
    3. Alice checks in Foo.uasset on branch main/A
    4. Bob can now check out Foo.uasset on branch main/B, which he does
    5. Bob checks in Foo.uasset on main/B
    6. Admin tries to merge branches A and B into main, but there is a merge conflict for the unmergeable Foo.uasset - why did we even bother with locks in the first place?

    How it SHOULD work:
    1. Alice checks out Foo.uasset on main/A
    2. Alice checks in Foo.uasset on main/B
    3. Bob tries to check out Foo.uasset, but it fails because it has been locked on a revision that is later than the revision of branch B's current Foo.uasset
    4. Bob merges main/A into main/B, or cherry-picks the changeset where Alice checked-in Foo.uasset.
    5. Bob can now check out Foo.uasset, because the Foo.uasset *revision* on *his* branch corresponds with the *newest* *checkout* of Foo.uasset on *any* branch.

    In essence: When you check out a lockable file, it should prevent others from checking it out until they have updated to your check-out's corresponding check-in.

  19. 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 →
    Max Pixel shared this idea  · 
  20. 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 →
    Max Pixel shared this idea  · 
← Previous 1