Git commit Vs RTC changeset & RTC baseline
In git, every commit has a link to one or more previous commits so any commit represents the entire state of the repository at that commit. However what I notice in RTC is that the changesets seem to be independent of one another except when a file is modified by more than one changeset in which case the first changeset becomes the dependency for the second. Since the changesets are independent they don't describe the state of the repository but only the delta. Now I can see that changeset is not exactly equal to a git commit. RTC baseline represents a state of the repository but is a new baseline dependent on an existing baseline? Also is there a way I can look at the repository state at a given older time when there are no baselines available?
One answer
in RTCÂ a baseline represent the freeze of your configuration, a component in RTC (could be a repository)
depending of your configuration settings a baseline could be created by anyone or only an admin.
So feel free and create as much as possible baselines for each freeze you think or not think you can need in future.
That's the way for RTC.
Whit out baselines: you need to start with a stream or work space starting with the initial baseline (created automatically) and add your change sets on top,
,need to query for the change set with date