Date: Sat, 13 Jan 2001 14:51:20 -0800 (PST) From: Matt Dillon <dillon@earth.backplane.com> To: Mark Murray <mark@grondar.za> Cc: Robert Watson <rwatson@FreeBSD.ORG>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/etc crontab rc src/etc/defaults rc.conf src/etc/mtree BSD.root.dist src/libexec Makefile src/libexec/save-entropy Makefile save-entropy.sh Message-ID: <200101132251.f0DMpKS36028@earth.backplane.com> References: <200101132228.f0DMSN135897@earth.backplane.com> <200101132237.f0DMbbI21558@gratis.grondar.za>
next in thread | previous in thread | raw e-mail | index | archive | help
:> Committing your fixes can't make it any worse then it already is. :> The only reason I haven't committed anything yet is because I still hold :> out hope that one of the authors will unbreak the tree. : :I'll commit it when it it is ready. : :M :-- :Mark Murray If we are going to have to wait, then please commit a stopgap -- Warner's preloading patch, for example. There is absolutely no reason to leave the tree in a broken state this long. The tree should NEVER be left in a broken state by a commit when the brokedness is known immediately, as it is here. Do you really think it is appropriate to commit something to the tree that blows developers up (on top of something that is already blowing developers up), then spend a week debating how to do it right without either (a) backing out the commit or (b) committing a stopgap workaround while you debate the issue? I sure don't. If that's your attitude then maybe we should backout ALL the work... revert it all the way back to 4.2. If you don't commit *something* by sunday evening, I AM going to commit a stopgap. -Matt 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?200101132251.f0DMpKS36028>