From: Erik Mouw <erik@harddisk-recovery.com>
To: xan2@ono.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [License of kernel components] linux-2.x.y/Documentation/logo.GIF should be logo.PNG?
Date: Tue, 23 Dec 2003 17:16:56 +0100 [thread overview]
Message-ID: <20031223161656.GC26750@bitwizard.nl> (raw)
In-Reply-To: <178ed117d672.17d672178ed1@ono.com>
On Tue, Dec 23, 2003 at 04:20:07PM +0100, xan2@ono.com wrote:
> I believe that the tux logo located at
> linux-2.6.0/Documentation/logo.gif is the image that appears on the
> boot of the system if framebuffer is enabled, isn't it?
>
> In this cas, and also if it's only for documentation purpose, I think
> that we could change the propietary (and I think patented) format of
> this logo (gif) to anyone that were free (for example like PNG format
> [that has GPL licensed]).
AFAIK the GIF patent (or rather: the LZW patent) expired a year ago, so
I don't think it's an issue anymore.
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
next prev parent reply other threads:[~2003-12-23 16:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 15:20 [License of kernel components] linux-2.x.y/Documentation/logo.GIF should be logo.PNG? xan2
2003-12-23 16:16 ` Erik Mouw [this message]
2003-12-23 17:07 ` Gene Heskett
2003-12-23 19:12 ` Remove superflous copy of logo in /Documentation John Bradford
2003-12-23 19:38 ` [License of kernel components] linux-2.x.y/Documentation/logo.GIF should be logo.PNG? Erik Andersen
2003-12-23 20:45 ` Ian Hastie
2003-12-23 21:43 ` Edesio Costa e Silva
-- strict thread matches above, loose matches on Subject: below --
2003-12-23 22:27 xan2
2003-12-26 17:48 ` Paulo Marques
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=20031223161656.GC26750@bitwizard.nl \
--to=erik@harddisk-recovery.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xan2@ono.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.