From: Harald Arnesen <harald@skogtun.org>
To: tom st denis <tomstdenis@yahoo.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Gabriel Paubert <paubert@iram.es>,
linux-kernel@vger.kernel.org
Subject: Re: 0xdeadbeef vs 0xdeadbeefL
Date: Thu, 08 Jul 2004 01:17:36 +0200 [thread overview]
Message-ID: <87iscz9zlb.fsf@basilikum.skogtun.org> (raw)
In-Reply-To: <20040707185340.42091.qmail@web41112.mail.yahoo.com> (tom st denis's message of "Wed, 7 Jul 2004 11:53:40 -0700 (PDT)")
tom st denis <tomstdenis@yahoo.com> writes:
> Point is 0xDEADBEEFUL is just as simple to type and avoids any sort of
> ambiguitity. It means unsigned long. No question about it. No having
> to refer to subsection 12 of paragraph 15 of section 23 of chapter 9 to
> figure that out.
If people write either 0XdeadbeefUL or 0xDEADBEEFul, fine. But this is a
place where character case really makes a difference in readibility-
> Why people are fighting over this is beyond me. Fine, write it as
> 0xDEADBEEF see what the hell I care. Honestly. Open debate or what?
>
> And I don't need mr. Viro coming down off his mountain saying "oh you
> fail it" because I don't know some obscure typing rule that I wouldn't
> come accross because *** I AM NOT LAZY ***. Hey mr. Viro what have you
> contributed to the public domain lately? Anything I can harp on in
> public and abuse?
I think you will find that mr. Viro has contributed quite a lot :-)
--
Hilsen Harald.
next prev parent reply other threads:[~2004-07-07 23:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 21:56 0xdeadbeef vs 0xdeadbeefL David Eger
2004-07-07 0:06 ` tom st denis
2004-07-07 3:00 ` viro
2004-07-07 11:10 ` tom st denis
2004-07-07 11:18 ` Prohibited attachment type (was 0xdeadbeef) Richard B. Johnson
2004-07-07 11:48 ` tom st denis
2004-07-07 12:29 ` Jakub Jelinek
2004-07-08 5:52 ` Pavel Machek
2004-07-08 14:03 ` Jakub Jelinek
2004-07-07 12:13 ` R. J. Wysocki
2004-07-07 14:22 ` 0xdeadbeef vs 0xdeadbeefL viro
2004-07-07 18:47 ` tom st denis
2004-07-07 16:30 ` Gabriel Paubert
2004-07-07 18:41 ` tom st denis
2004-07-07 18:47 ` Christoph Hellwig
2004-07-07 18:53 ` tom st denis
2004-07-07 23:17 ` Harald Arnesen [this message]
2004-07-08 6:15 ` David Weinehall
2004-07-08 9:32 ` [OT] " Gabriel Paubert
2004-07-08 11:15 ` viro
2004-07-08 11:55 ` Gabriel Paubert
2004-07-08 16:41 ` Andries Brouwer
2004-07-08 17:13 ` Michael Driscoll
2004-07-08 17:16 ` Horst von Brand
2004-07-10 1:52 ` Andrew Rodland
2004-07-07 0:38 ` Richard B. Johnson
2004-07-07 4:52 ` David Eger
2004-07-07 11:40 ` Richard B. Johnson
-- strict thread matches above, loose matches on Subject: below --
2004-07-07 2:05 Ray Lee
2004-07-07 3:02 ` viro
2004-07-07 5:58 ` Alexandre Oliva
2004-07-07 6:12 ` Ray Lee
2004-07-07 5:55 ` Alexandre Oliva
2004-07-07 6:08 ` Ray Lee
2004-07-07 6:48 ` viro
2004-07-07 17:58 ` Alexandre Oliva
2004-07-12 17:31 ` H. Peter Anvin
2004-07-07 7:30 ` Tomas Szepe
2004-07-07 14:34 ` Jan-Benedict Glaw
2004-07-12 17:50 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iscz9zlb.fsf@basilikum.skogtun.org \
--to=harald@skogtun.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paubert@iram.es \
--cc=tomstdenis@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.