From: Jose Celestino <japc@co.sapo.pt>
To: linux-kernel@vger.kernel.org
Subject: Re: [STUPID] Best looking code to transfer to a t-shirt
Date: Fri, 3 Jan 2003 13:26:04 +0000 [thread overview]
Message-ID: <20030103132604.GE26258@co.sapo.pt> (raw)
In-Reply-To: <Pine.LNX.4.44.0301031419560.11311-100000@dns.toxicfilms.tv>
Words by Maciej Soltysiak [Fri, Jan 03, 2003 at 02:25:09PM +0100]:
> 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?
>
[root@morgoth:/usr/src/linux]# egrep -ir "( fuck)|( shit)" *
and choose.
--
Jose Celestino | http://xpto.org/~japc/files/japc-pgpkey.asc
----------------------------------------------------------------
"Don't summarize. Don't abbreviate. Don't interpret." -- djb
next prev parent reply other threads:[~2003-01-03 13:20 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 [this message]
2003-01-03 14:55 ` Matthias Schniedermeyer
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=20030103132604.GE26258@co.sapo.pt \
--to=japc@co.sapo.pt \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox