-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Feb 15, 2007, at 02:23, Bucky Katz wrote:

> Michael Lorenz <macallan@netbsd.org> writes:
>
>> It got removed from -current, AFTER 4.0 was branched so the first
>> release with the new threading code will be 5.0 which will probably
>> happen in 2008 or later. Unless you're using -current in whatever
>> product you're working on you have plenty of time to adjust and
>> whatever fixes you come up with will be useful for the 4.0 branch.
>> I would understand such an outcry if a change like that had happened 
>> on
>> a release branch but - well - it didn't.
>
> Guess who has to work in -current because the arm port maintainer
> didn't commit the OMAP architecture in time for it to make the 4.0
> branch?

And how exactly does that force you to use -current? Nothing keeps you 
from applying your fixes to the 4.0 branch. I didn't follow the OMAP 
changes, mainly because that's not exactly my work area but if you tell 
me what exactly needs to be pulled into 4.0 ( ideally in terms of 
commit messages on source-changes@netbsd.org ) I'll see to it - should 
be trivial, the branch isn't exactly old.
Anyway, you're right about the maintainer problem.

Besides that - how does your code depend on SA threads?

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBRdQSmspnzkX8Yg2nAQK/1AgAukCtJrwPoMZcp63NAx7bHvyg33b69SMP
Mb4DA0CFlegyo/RKvTjonWIE5oHhjcDV5bVZqDNu9Pje1bxJiJ8e5XGnmsV5iSHy
bJueslk4WMWll7orc+3ZjhW/nw6lDl3suZKvFBbbUYGPW5D8CMz8F3gZuDAVogwW
cOrRAm0zF6b+MqxVab0zaRfUVU9rZ7CWjoDE3jGA3amGO10FQWh0f7AwTQcvWp67
99ydq1YhQuoo5n4lP/MBUrIJPfIcSf2VCTWn72NmDFVn6/9TI72xzfhUQEu+ALGq
e8Fmp/pYB6QfCnfLd/KRnuHT+qZyZBGke4XSu5ZfgoXMKfI+xKexMQ==
=bw4P
-----END PGP SIGNATURE-----