Subject: Re: the path from nathanw_sa -> newlock2
To: Bucky Katz <email@example.com>
From: Michael Lorenz <firstname.lastname@example.org>
Date: 02/15/2007 02:58:17
-----BEGIN PGP SIGNED MESSAGE-----
On Feb 15, 2007, at 02:23, Bucky Katz wrote:
> Michael Lorenz <email@example.com> 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
>> 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
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 firstname.lastname@example.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?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
-----END PGP SIGNATURE-----