jstarrdewar Posted April 30, 2016 Report Share Posted April 30, 2016 So I've noticed a frustrating problem, and I'm wondering what the solution is: The changeset numbers are not consistent between different machines. On my computer's local server I see changesets labeled 0, 4, 5 On the cloud server I see changesets labeled 0, 2, 3 On my coworker's machine that just pulled down from the cloud I see changesets labeled 0, 1, 2 Of course these are all the same changesets. Not only that, but the dates and timestamps are different (I assume because we are in different timezones). So how are we supposed to be able to talk about specific changesets with each other, if everyone has a different numbering scheme? Is there something obvious that I'm overlooking? Link to comment Share on other sites More sharing options...
manu Posted May 3, 2016 Report Share Posted May 3, 2016 Using the changeset GUID: This unique identifier will not change with the replication operation, you can use it for the Branch Explorer filter and "cm find" operations. Link to comment Share on other sites More sharing options...
jstarrdewar Posted May 3, 2016 Author Report Share Posted May 3, 2016 Thanks Manu Link to comment Share on other sites More sharing options...
manu Posted May 6, 2016 Report Share Posted May 6, 2016 You are very welcome! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.