From: Gene Heskett <gene.heskett@gmail.com>
To: Lin Ming <mlin@ss.pku.edu.cn>
Cc: djwong@djwong.org, Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, josh@joshtriplett.org
Subject: Re: [PATCH] logo: Change regular 224-color tux logo to something more appropriate for Linux 3.1
Date: Sat, 10 Sep 2011 10:03:38 -0400 [thread overview]
Message-ID: <201109101003.38935.gene.heskett@gmail.com> (raw)
In-Reply-To: <CAF1ivSbWg4+wO6sj+6w5CtG=KsF89mhHkop1FY+JF6D9cwzoUw@mail.gmail.com>
On Saturday, September 10, 2011, Lin Ming wrote:
>On Sat, Sep 10, 2011 at 4:55 PM, <djwong@djwong.org> wrote:
>> For Linux 3.1, I thought we could change the 224-color framebuffer logo
>> to something more apropos given the version number. As the patch is
>> quite large, I'm only inlining the changelog. 8)
>>
>> See http://djwong.org/docs/31-tuxlogo.patch for too-large-for-lkml
>> patch, http://djwong.org/docs/31-tuxlogo.png for a PNG logo, or
>
>Funny, does it look like Win98's logo?
Yes, entirely too much of an imitation. I will not contaminate my Linux
install with it.
Cheers, gene
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: <http://204.111.66.235:85/gene/>
"The human brain is like an enormous fish -- it is flat and slimy and
has gills through which it can see."
-- Monty Python
next prev parent reply other threads:[~2011-09-10 14:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-10 8:55 [PATCH] logo: Change regular 224-color tux logo to something more appropriate for Linux 3.1 djwong
2011-09-10 9:18 ` Geert Uytterhoeven
2011-09-10 13:14 ` Lin Ming
2011-09-10 14:03 ` Gene Heskett [this message]
2011-09-10 23:06 ` Valdis.Kletnieks
2011-09-12 21:06 ` markus reichelt
2011-09-13 16:45 ` Valdis.Kletnieks
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=201109101003.38935.gene.heskett@gmail.com \
--to=gene.heskett@gmail.com \
--cc=djwong@djwong.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlin@ss.pku.edu.cn \
--cc=torvalds@linux-foundation.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