Date: Fri, 16 Feb 2001 13:07:09 -0500 From: Will Andrews <will@physics.purdue.edu> To: Luigi Rizzo <luigi@FreeBSD.org> Cc: current@FreeBSD.org, developers@FreeBSD.org Subject: Re: cvs commit: src/sys/net bridge.c if_ethersubr.c src/sys/netinet if_ether.c ip_fw.c ip_fw.h ip_input.c ip_output.c Message-ID: <20010216130708.M22030@london.physics.purdue.edu> In-Reply-To: <200102070103.f1713EE20280@freefall.freebsd.org>; from luigi@FreeBSD.org on Tue, Feb 06, 2001 at 05:03:14PM -0800 References: <200102070103.f1713EE20280@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 06, 2001 at 05:03:14PM -0800, Luigi Rizzo wrote: > Modified files: (Branch: RELENG_4) [...] A few days later... [...] On Sat, Feb 10, 2001 at 16:10:13PM -0800, Luigi Rizzo wrote: > Modified files: [...] What the heck is going on here? You committed code to -STABLE first then merged it to -CURRENT? I don't mind that you are testing bugfixes, but PLEASE do them in -CURRENT first! After all this is on our list of rules: <excerpt from http://www.freebsd.org/tutorials/committers-guide/article.html>: 8. The FreeBSD Committers' Big List of Rules [...] 6. 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. [...] Are we now breaking these rules? I've never broken this rule, and seldom has it been done in the past. -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010216130708.M22030>