Why are scripts being branched?


To understand why scripts get branched, it is important to understand that each sync script represents one iteration of the project. Each iteration is stored in history and each member's history is identical. Also, there is a "pecking order" among members. They are ordered by their user id. The top dog is the one with the lowest id (often 0).

A script is branched when two scripts miss each other, more specifically when more than one person performs a check-in against the same project state. (It's always a good idea to check your e-mail before doing a check-in. This doesn't always work, because there are sometimes large delays in e-mail.)

 

See also:

Conflicts and Branches