From: Matthias Schniedermeyer <ms@citd.de>
To: Maciej Soltysiak <solt@dns.toxicfilms.tv>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [STUPID] Best looking code to transfer to a t-shirt
Date: Fri, 3 Jan 2003 15:55:14 +0100 [thread overview]
Message-ID: <20030103145514.GA5566@citd.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0301031419560.11311-100000@dns.toxicfilms.tv>
On Fri, Jan 03, 2003 at 02:25:09PM +0100, Maciej Soltysiak wrote:
> Hi,
>
> I am in a t-shirt transfering frenzy and was wondering which part of the
> kernel code it would be best to have on my t-shirt.
> I was looking at my favourite: netfilter code, but it is to clean, short
> and simple functions, no tons of pointers, no mallocs, no hex numbers, too
> many defines used. I was looking for something terribly complicated and
> looking awesome to the eye.
>
> How about we have a poll of the most frightening pieces of the kernel ?
> What are your ideas?
egrep -ir "(on fire)" *
drivers/usb/printer.c:static char *usblp_messages[] = { "ok", "out of paper", "off-line", "on fire" };
:-)
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
next prev parent reply other threads:[~2003-01-03 14:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 13:25 [STUPID] Best looking code to transfer to a t-shirt Maciej Soltysiak
2003-01-03 13:26 ` Jose Celestino
2003-01-03 14:55 ` Matthias Schniedermeyer [this message]
2003-01-03 15:03 ` Anders Gustafsson
2003-01-03 15:11 ` Tomas Szepe
2003-01-03 15:59 ` Disconnect
2003-01-03 16:32 ` Randy.Dunlap
2003-01-03 16:53 ` Arnaldo Carvalho de Melo
2003-01-03 16:33 ` Alvaro Lopes
2003-01-03 22:58 ` Rik van Riel
2003-01-03 23:39 ` William Lee Irwin III
2003-01-04 0:20 ` Ranjeet Shetye
2003-01-04 13:46 ` Maciej Soltysiak
2003-01-04 13:47 ` Maciej Soltysiak
2003-01-05 3:55 ` Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2003-01-03 14:53 uaca
2003-01-04 0:13 Nivedita Singhvi
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=20030103145514.GA5566@citd.de \
--to=ms@citd.de \
--cc=linux-kernel@vger.kernel.org \
--cc=solt@dns.toxicfilms.tv \
/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.