submitted the fix.</entry>

		    submitted the fix; for committers, just the username on

		    the FreeBSD cluster.</entry>

		    that reviewed the change.  If a patch was submitted to a

		    that reviewed the change; for committers, just the

		    mailing list for review, and the review was favorable,

		    username on the FreeBSD cluster. If a patch was

		    then just include the list name.</entry>

		    submitted to a mailing list for review, and the review

		    was favorable, then just include the list name.</entry>

		    that approved the change.  It is customary to get prior

		    that approved the change; for committers, just the

		    approval for a commit if it is to an area of the tree to

		    username on the FreeBSD cluster. It is customary to get

		    which you do not usually commit.  In addition, during the

		    prior approval for a commit if it is to an area of the

		    run up to a new release all commits

		    tree to which you do not usually commit.  In addition,

		    <emphasis>must</emphasis> be approved by the release

		    during the run up to a new release all commits

		    engineer.  If these are your first commits then you should

		    <emphasis>must</emphasis> be approved by the release

		    have passed them past your mentor first for approval, and

		    engineering team.  If these are your first commits then

		    you should list your mentor.</entry>

		    you should have passed them past your mentor first, and

		    you should list your mentor, as in

		    ``<replaceable>username-of-mentor</replaceable>

		    <literal>(mentor)</literal>''.

                 </entry>