svn commit: r205014 - in head: . sys/amd64/amd64 sys/amd64/conf sys/amd64/include sys/amd64/linux32 sys/compat/freebsd32 sys/compat/ia32 sys/conf sys/fs/procfs sys/ia64/conf sys/ia64/ia64 sys/ia64/...

[Carlos A. M. dos Santos]

On Fri, Mar 12, 2010 at 10:52 AM, Rui Paulo <rpaulo at freebsd.org> wrote:
>
> On 12 Mar 2010, at 21:36, Carlos A. M. dos Santos wrote:
>
>> On Thu, Mar 11, 2010 at 11:49 AM, Nathan Whitehorn
>> <nwhitehorn at freebsd.org> wrote:
>>>
>>> Author: nwhitehorn
>>> Date: Thu Mar 11 14:49:06 2010
>>> New Revision: 205014
>>> URL: http://svn.freebsd.org/changeset/base/205014
>>>
>>> Log:
>>>  Provide groundwork for 32-bit binary compatibility on non-x86 platforms,
>>>  for upcoming 64-bit PowerPC and MIPS support. This renames the
>>> COMPAT_IA32
>>>  option to COMPAT_FREEBSD32, removes some IA32-specific code from MI
>>> parts
>>>  of the kernel and enhances the freebsd32 compatibility code to support
>>>  big-endian platforms.
>>
>> COMPAT_FREEBSD32 is an unfortunate choice. It can be easily
>> interpreted as "compatible with FreeBSD 3.2". Something like
>> "COMPAT_32BIT" would be more meaningful.
>
> There's a lengthy discussion about this on another mailing list.
>
> This is unlikely to be changed and emailing the committer who provided
> valuable time on this code wastes his time and everyone else's.

So the user - the person to whom the software is made, theoretically -
don't have the right to disagree when he sees a change that looks
confusing "because the committers's time is too valuable". Sorry, I
was not aware of that policy. Please forgive my audacity. Keep in mind
that we, the users, are a bunch of idiots that don't like to become
astonished by sudden changes in the meaning of the symbols that we use
to see. Thanks God we have you, the holly committers to protect us
from our own ignorance.

-- 
Not so young, but still crying out
Full of anger full of doubt