Jump to content

Search the Community

Showing results for tags 'lock'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Plastic SCM
    • General
    • Installation and configuration
    • Unity 3D
    • Plastic SCM on Mac
    • Plastic SCM on Linux
    • Gluon
    • Git interop
    • Integrations
    • Community Edition
    • Branching and merging
    • Announcements
  • Plastic SCM 4.0 Beta (Closed)
  • Plastic Cloud
    • General
    • Configuration
  • SemanticMerge
    • General
    • License
    • SCM's configuration
    • Share your experience!
    • External Parsers
  • GitJungle
  • Method History for Subversion
  • PlasticX Early Adopter Program's General Feedback
  • PlasticX Early Adopter Program's Issue Reporting
  • PlasticX Early Adopter Program's Feature Requests
  • PlasticX Early Adopter Program's Announcements

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 3 results

  1. Hi! I'm new to PlasticSCM and am setting up a new repository on the cloud service. I'm a developer using the PlasticSCM client proper, which is working fine... but when I set up Gluon for our artist, I'm getting weird errors. Several hundred files appear to be locked and checked out to the artist. The Check In option isn't available. And when we try Check Out, there's an error message saying "These items are exclusively checked out by [artist name]." Is there anyway to reset the checkouts on these files? Thanks, Brian
  2. Hello! I was hoping someone could help clarify this for me. What exactly is the difference between clicking "Check out" and "Lock and check out"? Looking through the Gluon documentation it says that "By selecting the Checkout option, the files you selected will lock and nobody will be able to edit them until you check them back in." If that's the case then the files you check out are locked anyway. It sounds like the only difference between the two is whether the lock takes place, before or after checking out the files. If so, what are the benefits of doing it one way over the other? Thanks! -Miranda
  3. We have recently set up a project where a directory within that project is an xlink to another project. The files within this xlink are meant to never be edited, so we have the xlink on read-only. Whilst this is fine to prevent any changes to the files on source control, we need to enforce that our users cannot modify the files locally at all. Ideally this would be with a windows file lock applied recursively to the directory. Is there a convention for doing this within plastic? The closest idea I have is to use client-side triggers to file lock the directory, but I cant see a way of applying the trigger to a single repository? It feels like I am probably missing an element of Plastic SCM to solve this problem? Any help much appreciated! Thanks
×
×
  • Create New...