[adding scm-migration-dev] For the scm-migration-dev folks, we've been discussing how the checks should handle workspaces that have multiple outgoing changesets...
>>>>> "Rich" == Richard Lowe <richlowe at richlowe.net> writes: Rich> However, if we default to checking each changeset individually, we Rich> run into people (like me) who run pbchk and nits often, and see Rich> warnings from changeset N-1 about problems fixed in N. Which is Rich> just as bad. Perhaps this should be a semantic difference between "nits" and "pbchk". "nits" could do the checks as of the final changeset, and "pbchk" could check each changeset. Rich> (note that the gate side of things should always take the Rich> changeset-at-a-time viewpoint, and either disallow multiples, or Rich> check them discreetly). Agreed. mike
