From owner-cvs-all Fri Jul 13 14: 1:37 2001 Delivered-To: cvs-all@freebsd.org Received: from coffee.q9media.com (coffee.q9media.com [216.94.229.19]) by hub.freebsd.org (Postfix) with ESMTP id DF48E37B403; Fri, 13 Jul 2001 14:01:30 -0700 (PDT) (envelope-from mike@coffee.q9media.com) Received: (from mike@localhost) by coffee.q9media.com (8.11.2/8.11.2) id f6DLHDv25225; Fri, 13 Jul 2001 17:17:13 -0400 (EDT) (envelope-from mike) Date: Fri, 13 Jul 2001 17:17:13 -0400 (EDT) Message-Id: <200107132117.f6DLHDv25225@coffee.q9media.com> From: Mike Barcroft To: Jordan Hubbard Cc: tobex@tobez.org, sobomax@FreeBSD.org, dd@FreeBSD.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: Another immediate MFC that isn't really necessary [was: cvs commit: src/libexec/talkd announce.c] Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jordan Hubbard writes: > I don't think so, and it really should be in the committer's guide. > That's a strong hint to the folks who implemented it. :) No, it's in there. Section 8, Rule 7: Changes go to -CURRENT before -STABLE unless specifically permitted by the release engineer or unless they're not applicable to -CURRENT. Any non-trivial or non-urgent change which is applicable should also be allowed to sit in -CURRENT for at least 3 days before merging so that it can be given sufficient testing. The release engineer has the same authority over the -STABLE branch as outlined for the maintainer in rule #5. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message