Date: Sat, 28 Jun 2003 15:03:07 -0500 From: David Leimbach <leimy2k@mac.com> To: Julian Elischer <julian@elischer.org> Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: new KSE signal code Message-ID: <890E3745-A9A3-11D7-B882-0003937E39E0@mac.com> In-Reply-To: <Pine.BSF.4.21.0306281219320.2537-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Because we aren't working on anything and need something to do... so we find ways to think about how we can enforce quality without understanding how stuff works first maybe? :) Just a guess. Dave On Saturday, June 28, 2003, at 02:20 PM, Julian Elischer wrote: > he means that between the time the commits start and finish there may > be > an inconsistant period.. Why is everyone so eager to jump down everyone > else's throat these days? > > > On Sat, 28 Jun 2003, David Schultz wrote: > >> On Sat, Jun 28, 2003, David Xu wrote: >>> I begin to commit KSE signal code, libkse will >>> be broken for a while. >> >> Umm...if it's known to be broken, then why did you commit it? >> If you want people to test KSE and report bugs, the version in >> the tree needs to be of consistently good quality. >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to >> "freebsd-current-unsubscribe@freebsd.org" >> > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?890E3745-A9A3-11D7-B882-0003937E39E0>