Libthr should be working again.
--
Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc
[EMAIL PROTECTED] | D228 1A6F C64E 120A A1C9 A3AA DAE1 E2AF DBCC 68B9
[EMAIL PROTECTED]| FreeBSD - The Power To Serve
___
[EMAIL PROTECTED] mailing list
htt
In article <[EMAIL PROTECTED]>,
Mike Makonnen <[EMAIL PROTECTED]> wrote:
> David's signal changes broke libthr. This is not his fault. The
> original implementation of sigtimedwait was broken and jdp (John
> Polstra) had worked up patches to fix it, but David beat him to it
> :-).
Well, it would
gt;
Cc: "David Xu" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Saturday, June 28, 2003 8:42 PM
Subject: Re: HEADS UP: new KSE signal code
I don't think you understand what I believe he was trying to say.
Commits to CVS are NOT atomic therefore getting a copy of FBS
ested
widely.
Thank you again,
David Xu
- Original Message -
From: "David Leimbach" <[EMAIL PROTECTED]>
To: "David Schultz" <[EMAIL PROTECTED]>
Cc: "David Xu" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Saturday, June 28, 2003 8:4
On Saturday, June 28, 2003, at 3:18PM, David Schultz wrote:
On Sat, Jun 28, 2003, David Leimbach wrote:
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?
Umm...no, but than
David's signal changes broke libthr. This is not his fault. The original
implementation of sigtimedwait was broken and jdp (John Polstra) had worked up
patches to fix it, but David beat him to it :-). Libthr depended on the old
"broken" semantics of sigtimedwait, so any applications using libthr wi
On Sat, Jun 28, 2003, David Leimbach wrote:
> 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?
Umm...no, but thanks for the insult. How about: Because we are
wor
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 th
On Sat, Jun 28, 2003, 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?
The statement that ``libkse will be broken for a while'' gave me
the impress
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, libk
I don't think you understand what I believe he was trying to say.
Commits to CVS are NOT atomic therefore getting a copy of FBSD in
between David's
start and finish of commits would be broken.
When he says he is finished.. I bet it will work again.
Now if we were all using Perforce this would b
Finished!
- Original Message -
From: "David Xu" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, June 28, 2003 2:56 PM
Subject: HEADS UP: new KSE signal code
I begin to commit KSE signal code, libkse will
be broken
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.
__
I begin to commit KSE signal code, libkse will
be broken for a while.
David Xu
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
14 matches
Mail list logo
