Jump to content

psantosl

Members
  • Content Count

    923
  • Joined

  • Last visited

  • Days Won

    22

psantosl last won the day on May 31

psantosl had the most liked content!

Community Reputation

36 Excellent

About psantosl

  • Rank
    CTO - Plastic SCM

Contact Methods

  • Website URL
    https://blog.plasticscm.com

Profile Information

  • Gender
    Male
  • Interests
    plastic plastic plastic...

Recent Profile Visitors

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

  1. But main always have an initial changeset with the root dir. also, if you create a branch from another one, they share the same location (like Git) but it is not dynamic or anything. So, not sure why you need the intermediate changeset πŸ˜‰
  2. Thanks for the details, Aaron. It is a real pleasure and privilege to learn more about version control from experienced users. Regarding this: What would be your desired behavior? We changed how branches worked in Plastic eons ago, and I'm always eager to know about other options. We used to have some sort of branch inheritance where you could make a change to a parent branch and then changes were dynamically propagated to children if they didn't collide, and I used to love it, but it was extremely confusing for mostly everyone. So, please, share what your ideal behavior would be. pablo
  3. Branches start from a changeset. That’s why an empty branch behaves this way. you can play with permissions to deny people creating child branches, or you can create triggers to control the branch hierarchy That being said: do you have a Perforce background? And, why do you need this complex branch hierarchy? Have you read about our recommended branching pattern? https://www.plasticscm.com/book/#_a_perfect_workflow
  4. Hi Aaron, A top level branch is just a namespace convention. You can create "develop" starting from "main", and it will be called "develop" if it is a top-level branch while it would be "main/develop" if it was an ordinary branch. Other than that, their behavior is EXACTLY the same. Please share more about what you would like to achieve so we can find a better solution. From here it sounds a little bit like "git flow" πŸ˜‰ and it is probably too many structure branches to me, but that's just an opinion πŸ˜‰ pablo
  5. Hi Fleer, Well, this is a pretty interesting topic. In fact, it is worth a blogpost and a chapter in the Plastic book. I just feel dumb I didn't write it. There are different possible options: a) An after-update trigger that launches the update under projects behind the scenes for them each time they update something. b) Force them to work with Plastic and work on the main branch => then they must update. But probably not a good choice. There are other options but they are more in the structure side of things, not really in "forcing users to update". Let me know if a) makes sense, and I'll share this with the team. pablo
  6. Hi Milan! Thank you for your kind words πŸ™‚
  7. Well, we *should* be good detecting moves, but we are better with code because then we can calculate similarity. We have a way to use the NTFS underlying logs to detect moves more precisely, but we never made it public.
  8. That's what you can customize: How do you move the pngs? Using some tool? Or directly in Explorer? If the latter, you can always use the Plastic Workspace Explorer for the moves
  9. Wow, this is a weird one. Check the server logs. Maybe plastic.errors.log.txt gives us a hint.
  10. Hi, You can achieve that using the command line, where you can do "cm mv" even after the move was actually done. From the GUI, you can do the moves "beforehand" using CTRL-X/CTRL-V in the Workspace Explorer. Now, would you mind sharing why the move detection didn't work fine for you? Thanks, pablo
  11. Hi, We don't allow to do that, but it is certainly doable removing the creds entry from client.conf. Maybe you can create a small script that removes that config part every few minutes. BUT, you'd have to close the GUI. Makes sense?
  12. Hi Marc, First, very sorry for this issue. I take full responsibility on this because this is a known bug that I personally decided not to fix yet. Now, here goes a workaround. Go to your workspace. Go into the hidden directory .plastic. Show me your plastic.selector. It must be a branch, not a changeset. Does it look like this? >type plastic.selector rep "quake@localhost:6060" path "/" smartbranch "/main" If it does, you are good to go. If not, remove the "changeset" part and leave the branch. Close your GUIs. Delete (or backup) the plastic.wktree file inside this plastic hidden directory. This is the workspace metadata, and the one causing the problem. Now open the GUI, go to workspace explorer and click "update". Plastic will rehash your files, won't download much, and you'll be good to go. Let me know if it helps. pablo
  13. Hi Elite PopCorn, Unfortunately no, we don't have an amend option. But, yes, more and more people is asking for it. In fact, I'd like to track somehow how many are really interested: why don't you vote here? https://plasticscm.uservoice.com/forums/15467-general/suggestions/5221214-amend-commits
  14. psantosl

    sync bug

    Thanks for the kind words. It is extremely encouraging for the entire team that you take a minute to share such kind words. Thanks.
×
×
  • Create New...