Jump to content

psantosl

Members
  • Content Count

    929
  • Joined

  • Last visited

  • Days Won

    23

psantosl last won the day on September 27

psantosl had the most liked content!

Community Reputation

37 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. Hi @wouter, There are two things here: regarding the locks that get wrongly applied between repos, we are currently checking this. I think you also requested this in Zendesk. We are on it. Regarding your suggestion about keeping locks per branch: yes, it makes a lot of sense. I mean, it is not our final goal, we'd like to have locks applied between branches and released only when the file reaches a given branch in a given repo, but so far being able to keep locks per branch makes a lot of sense. Not sure, though, if we'll be able to develop it asap.
  2. Did you find "checkin to different branch"? Or, move cset to a different branch:
  3. But you don't need a workspace for cm ls. You can pass it "server side" paths. Use the --tree option. That's the key.
  4. Hi Mikael, I'm not sure if this will totally help, but why don't you try the cm ls --tree command? It lets you browse a given tree, even a given path or file on a tree, and you can find what was loaded on a given changeset. Run cm ls --help, here goes one of the examples: cm ls /code --tree=ae1390ed-7ce9-4ec3-a155-e5a61de0dc77@myrep@denver:7070 Let me know if it helps (I activated notification of replies this time, so it won't take that long to reply, sorry for that) pablo
  5. You can do a cm find revision and then filter by path with the item field, if I’m not mistaken. you can also check the history of the directory since the directory changes each time its children change, the result is quite easy to obtain
  6. 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 πŸ˜‰
  7. 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
  8. 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
  9. 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
  10. 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
  11. Hi Milan! Thank you for your kind words πŸ™‚
  12. 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.
  13. 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
×
×
  • Create New...