HEADS UP: new KSE signal code

[David Leimbach]

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 at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to 
>> "freebsd-current-unsubscribe at freebsd.org"
>>
>
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to 
> "freebsd-current-unsubscribe at freebsd.org"