Subject: Re: the path from nathanw_sa -> newlock2
To: Bucky Katz <firstname.lastname@example.org>
From: Michael Lorenz <email@example.com>
Date: 02/15/2007 01:32:40
-----BEGIN PGP SIGNED MESSAGE-----
On Feb 15, 2007, at 01:04, Bucky Katz wrote:
> As I said, when we started out, we tried posting on relevant mailing
> lists, and got zero feedback. When no one listens, you stop talking.
Yeah, nobody seems to read firstname.lastname@example.org, for whatever reason. I
didn't get any feedback on my Shark stuff either.
>> Please, it would be nice if this silly bickering could stop, and we
>> could simply start communicating effectively.
> Please stop sending me emails accusing me of "shouting". Please stop
> pretending to more knowledge about what's going on wrt to this issue
> than you actually have. Please stop being defensive. All of those
> would be good steps towards more effective communication.
Would you please both get a grip? Fingerpointing and tossing
accusations at each other isn't exactly 'effective communication'.
> I have no way to "solve" this problem. The NetBSD foundatation,
> without consultation with the development community, has arbitrarily
> removed functionality from the kernel. As far as I can see you've got
> no intention of reversing that decision or even defering it and asking
> for that input.
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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
-----END PGP SIGNATURE-----