Date: Wed, 19 Mar 2008 13:27:54 -0400 From: David Schultz <das@FreeBSD.ORG> To: Paolo Pisati <piso@FreeBSD.ORG> Cc: cvs-src@FreeBSD.ORG, src-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/netinet/libalias alias_db.c alias_irc.c Message-ID: <20080319172754.GB44884@zim.MIT.EDU> In-Reply-To: <20080319165522.GA95772@tin.it> References: <200803191150.m2JBoj6j020138@repoman.freebsd.org> <20080319165336.GA44656@zim.MIT.EDU> <20080319165522.GA95772@tin.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 19, 2008, Paolo Pisati wrote: > On Wed, Mar 19, 2008 at 12:53:36PM -0400, David Schultz wrote: > > > > By the way, is any of this security-relevant, or is there a > > different reason why most of your recent commits have been > > insta-MFCed? Usually things are given a chance to sit in HEAD for > > a few days so that any problems get caught before the changes are > > MFCed. > > no, but the fix was trivial so i decided to MFC immediately. Yes, but isn't it the case that it's a fix for a bug in another change that also got insta-MFCed? The point is that even "trivial" changes often have unexpected problems, e.g., they don't compile for some random architecture, so it's often a good idea to let them settle to avoid breaking STABLE.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080319172754.GB44884>