Jump to content

S_Luis

Members
  • Content Count

    28
  • Joined

  • Last visited

  • Days Won

    1

S_Luis last won the day on June 10 2015

S_Luis had the most liked content!

Community Reputation

2 Neutral

About S_Luis

  • Rank
    Member

Recent Profile Visitors

1,267 profile views
  1. The relayout and visibility configuration files are simple and portable, so I think we can safely share them through the plastic-global-config repository to all users.
  2. @psantosl This is a client.conf flag, not a branchexplorer.conf flag. We can't put it in the global configuration.
  3. Just fixed it. Should be in release early next week Thank you again for reporting this!
  4. Ouch. Now I see what you meant in your first post, sorry! 😞 Yes, this is a bug. I will take care of it as soon as possible. Thank you for reporting it!
  5. Well, we have some sort of index... https://www.plasticscm.com/download/releasenotes/all that is not linked from anywhere - so I can't promise it will stay accessible forever!
  6. Hi Wolfram. Let me explain the cause of this label drawing: Try the following: when you right-click a label draw that represents a single label, you have a (let's call it this way) "top-level" contextual menu with all of the options for said label. On the other hand, when you right-click a label draw that represents two or more labels, you can see that instead of the "top-level" menu you have a menu to choose the label, and then a submenu with all of the options for said label. That's on Windows. On Linux and macOS we don't even draw multiple labels by splitting the crown - we just differentiate them by the names printed on top of them. On Windows, the multiple label crown just indicates the number of labels - but it doesn't differentiate which is which. Again, this comes from the times we didn't have color filters - but the search behaves in the exact same way. Try a search that only affects a label, and you'll see all of them highlighted. Right now maybe it is worth it to draw each piece of the crown with a different color depending on the filters that apply to each label - we'll look into it, but I can't promise it will make its way into the roadmap! About the case insensitive search - nope, sorry! You need to manually combine them.
  7. About this: I talked with the team and we are going to implement the following: a release notes portal in which you can select in a combobox an "origin" release, and another combobox to select the "destination" release. Then the page will give you all the release notes between those two versions (origin not included, I guess, as that's the one you have installed). Would that be useful for you and your team? I'm almost sure that can be achieved with some "cm find", exporting the results, and then some processing on your side to sort everything out. You can check the "cm find" online documentation here: https://www.plasticscm.com/documentation/cmfind/plastic-scm-version-control-query-system-guide
  8. There is no Branch Explorer legend anymore, except for the online documentation: https://www.plasticscm.com/documentation/gui/plastic-scm-version-control-gui-guide#ComponentsoftheBranchExplorerDiagram
  9. Hi Wolfram. We are sorry to hear you miss the Review & Stats section. We removed it back in version 8.0.16.3274, as indicated in the release notes: https://www.plasticscm.com/download/releasenotes/8.0.16.3274 We decided to remove the "Change Statistics" because it was Windows only, it didn't provide much information, and almost no one was using it. This is the first feedback we hear about this, almost four full months after removing the feature. Sadly there is no way to bring it back. It is not hidden behind a special argument nor another feature either in the clients or in the WebUI replaces it. Sorry! If this was in any way a key part of your workflow, please ask for us to bring it back in our UserVoice: https://plasticscm.uservoice.com/forums/15467-general If enough users feel this way, we can think in an overhaul for this feature :)
  10. If you have your workspace pointing to a cset instead of to a branch, this is what the cm status will show: > cm status cs:7024018@codice@skull.codicefactory.com:9095 (head:7024019) It won't show you the branch, but it will show changeset's branch's head. In my case, I have my workspace pointing to 7024018 and the head of the branch that changeset is in is 7024019. But you DON'T need to parse this output. Whether your workspace points to a branch or a changeset, just executing: > cm update --last ...Will switch your workspace to the current branch's head.
×
×
  • Create New...