Merging from the major branch

Because the main branch is the destination of the merges, developers work in a view with the default config spec. The situation is similar to the one described in To prepare to merge. This time, the merges take place in the opposite direction, from the major branch to the main branch. Accordingly, the findmerge command is very similar:

cleartool findmerge /vobs/monet /vobs/libpub -fversion /main/major/LATEST \
–merge –graphical
  .
  .
  .
A 'findmerge' log has been written to
"findmerge.log.23-Mar-99.14:11:53"

After checkin, the version tree of a typical merged element appears as in the following figure.

A version tree has two branches, main and major. — Figure 1: Element structure after the pre-Baseline-2 merge