Date: Fri, 31 Jan 2003 20:54:29 -0800 From: Jon Mini <mini@freebsd.org> To: Scott Long <scott_long@btc.adaptec.com> Cc: Julian Elischer <julian@elischer.org>, John Baldwin <jhb@freebsd.org>, cvs-committers@freebsd.org, cvs-all@freebsd.org, "Tim J. Robbins" <tjr@freebsd.org> Subject: Re: cvs commit: src/sys/kern subr_trap.c Message-ID: <20030201045429.GS27470@elvis.mu.org> In-Reply-To: <3E3AF6FD.4000904@btc.adaptec.com> References: <Pine.BSF.4.21.0301311326340.45015-100000@InterJet.elischer.org> <3E3AF6FD.4000904@btc.adaptec.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Scott Long [scott_long@btc.adaptec.com] wrote : > Without picking on David, I think that this is a perfect example of the > grumbling that has been building about the lessening quality of people's > work. Would a forced backout send the message that untested and broken > commits are not acceptable? I'm reluctant to lower the axe while David > is away, but it's put us in a bad position. I also agree that this should be backed out, but I don't think it's core's place to do that in this situation. We have a much more appropriate (and less heavy-handed) move we can make, which still sends the right message but doesn't slag anyone in the process. Julian, how about you back it out? As David's mentor, this is entirely appropriate for you to do, especially since he's away. Say something in the commit message like "backing these changes out due to bugs discovered while david was on vacation. As his mentor, I am backing them out until he can fix them." -- Jonathan Mini <mini@freebsd.org> http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030201045429.GS27470>