Mark J. Nelson writes: > If a development team is affected by a hideous problem that caused a > respin, it would be much more worth their time to pull up to the needed > fix from the main branch and merge, than to deal with divergence.
I suspect that the most useful thing the gatekeepers could publish would be a list of per-build changesets in the main branch that represent things that were pulled back to make a given build. That way, if someone really needs to know that his project gate is official snv_100 + plus project changes, he can pull with "-r" and then merge in the gatekeeper-supplied respin list of changesets. (Still seems weird to be using three digits for build numbers. At least we've got around 34 years and six months before we have to worry about four digit build numbers ...) -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
