Will Fiveash writes: > wx pbchk on the other hand was supposed to be run just prior to the > putback to the gate (a Teamware command similar to hg push). In > addition to nits checks and pbchk ran additional checks to make sure > there were no SCCS or other workspace issues that violated ON (think > Solaris) gate putback rules. The non-nits check warnings usually did > not require file content modification and thus did not require a > build/test after fixing the issue.
A key difference between "nits" and "pbchk" was that "nits" made checks that were entirely local, so you didn't need to be attached to a network or have an accessible parent gate in order to do it. "pbchk" required access to a network and the parent. That difference hasn't been preserved in going to hg. Pretty much everything involves accessing the parent, as that's the only way we get an 'active' list these days. I think it'd be nice to change that. -- 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
