Jump to content

Search the Community

Showing results for tags 'Gluon'.



More search options

  • 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

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 2 results

  1. Since Gluon defaults to have no files/folders added to your workspace, and seeing as there's probably a reason why someone is adding a workspace (i.e. to get files/folders), why not put you right into the configuration screen? This has stumbled a few people who didn't know why they weren't pulling any files and it's annoying to resolve it remotely since you have to go step-by-step verifying everything they've done.
  2. I made some bad commits, so using Plastic SCM on Workstation "A ", I deleted the changesets and updated my workspace to an earlier point. Working in Unreal Engine, I had to update thousands of binary assets, so I turned off version control... Unfortunately, when I went to SCM to check my files in, Workstation "B" happens to have many of these same assets checked out from one of the deleted changesets in Gluon. Now I can't checkin my changes on "A" because they're locked on "B" and I can't undo my changes and checkin the files on "B" because the changeset is gone. If I try to do an "Undo" in Gluon on the changed files, I get a message that the file can't be downloaded, was "probably" replicated with --nodata and is not in the repository. How can I force Workstation "B" to check in files it can't find in the repository in Gluon? Is there some way that I can abandon the workspace on "B" and re-create it? Thanks in advance! -Donald
×
×
  • Create New...