In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
> Sorry Poul, but you have no authority in this matter. All the statements
> you have made in the last hour simply point out, in very clear terms,
> that you don't know what you are talking about. Instead of simply
> admiting a mistake or even spending some time to review the code
> more closely, your solution is instead to continue to make outrageous
> statements.
The fact that I think the hacks should be kept firmly inside the
VM system, rather than spill out into the rest of the kernel is
not something I count amongst my mistakes.
I have actually spent quite some time looking at the code, both
before and again tonight just because of your email.
That is probably the best example of a review process which works.
> Frankly, Poul, I strongly, *STRONGLY* recommend that you simply not
> reply to any of my postings.
This has been my general policy for a long time, but it gets
overridden whenever you come up with something which is obviously
wrong. (And I find the fact that so many people have adopted this
policy disturbing, and sufficient grounds for me to relax my instance
of it.)
> Not a single one, because I am wholely
> sick and tired of your superiority complex. This thread was not meant
> for you, and your presence in it is not welcome. And don't even think
> about doing an end-run around me and committing your frankly inappropriate
> 'solution' - I'm going through proper channels to get this in.
I have all rights I need to answer you when you send an email in
public asking for a review.
It is my obligation to answer you when I am one of the few people
who are not intimidated by neither you nor the code in question
and I can see that what you are proposing is plain wrong.
So far you have one very experienced kernel programmer objecting
to your patch, so yes: you will bloddy have to go through proper
channels to resolve this issue.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
