Jump to content
Plastic SCM forums are now in Unity. Click here to open the new forum ×

kkl

Members
 View Profile  See their activity

  • Posts

    4

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

kkl's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Conversation Starter Rare
  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. kkl
    It shows a popup message saying "Item has either been deleted or is excluded by the current filter". Steps to reproduce: 1. Create a new branch. 2. Make some changes and check in. 3. Create New Code Review for this branch. 4. Add a change request in one of the files. 5. Rename/delete the file that has the change request and check in. 6. Double click the change request again. Why do we still need to view change request after the file is renamed/deleted? Here's the use case: Sometime we leave a change request to make some changes in the file, and another change request to rename the file. After renaming the file, other change requests in the same file are no longer available to view (showing the error popup as mentioned in the title), especially when the change request comment is too long to view the entire comment under the change request list. Plus, all the replies under that change request are not available to view as well.
  2. kkl
    For example, if I have latest changeset number "1000" in P4, I'd like to have this "1000" number as the first changeset number in Plastic. I did not go through the migrating P4 to Plastic process since I don't want the history. I just created a new repo and checked in the files into that repo directly.
  3. kkl
    I'm moving from Perforce to Plastic and would like sync the changeset number without migrating the history. Is it possible?
  4. kkl
    New user here. Unable to open PlasticSCM For Developer with error message "Object reference not set to an instance of an object. Plastic client can't continue and will be closed." in Windows 10. Then PlasticSCM closed. However, Gluon works fine. Here're the steps to reproduce: 1. First time user, go through Plastic SCM Client Configuration Wizard and login. 2. Select Plastic for Developer 3. Select "Distributed" at the top menu 4. Click "New" at Cloud Repository 5. Enter new repo name and click "OK" 6. Enter all required text fields e.g. Workspace name 7. Click "OK" 8. Another window pops up and show the error message. I've attached debug log here. Am I missing some steps that could cause this error? plastic.debug.log.20201128.txt plastic.relevant.log.20201128.txt
×
×
  • Create New...