Keith M Wesolowski writes: > On Tue, Mar 07, 2006 at 08:13:01AM -0800, UNIX admin wrote: > > > The reason I took up interest in the code gates is that some of the > > kernel engineering folks' posts seem to imply there's 'gatekeeper' > > logic of some sort sitting on a code gate, doing basic sanity checks > > on the putback source code. This is just what seems to have been > > implied. > > The gatekeeper is a person. One hopes that his actions are logical, > but they're not all programmatic. There are some checks that get run > automatically, and we're looking to clean up and perhaps expand those > to make use of the capabilities of whatever DSCM sysytem we end up > with.
As nobody's mentioned it in this thread... 'wx' takes care of most of the automatic checks, and can (must) be run by ON developers before putting the changes from their gates back into the main gate. It checks for things like cstyle compliance, workspace cleanliness, and copyrights. http://cvs.opensolaris.org/source/xref/on/usr/src/tools/scripts/wx.sh http://cvs.opensolaris.org/source/xref/on/usr/src/tools/scripts/wx.1 Not running 'wx pbchk' before putback often leads to embarassment and backout due to easily detectable errors. The gatekeepers have a set of scripts which also automatically check for these types of errors when a developer has putback changes (which Keith alluded to above). liane -- Liane Praza, Solaris Kernel Development [EMAIL PROTECTED] - http://blogs.sun.com/lianep _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
