From: <xan2@ono.com>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: linux-kernel@vger.kernel.org
Subject: RE: Re: [License of kernel components] linux-2.x.y/Documentation/logo.GIF should be logo.PNG?
Date: Tue, 23 Dec 2003 20:33:56 +0100 [thread overview]
Message-ID: <1a6d6d1a9664.1a96641a6d6d@ono.com> (raw)
On 23th (2003, 17:16), Erik Mouw <erik@harddisk-recovery.com> wrote:
>>Re: [License of kernel components] linux-2.x.y/Documentation/logo.GIF
should be logo.PNG?
>
> 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
>
Sorry, but I didn't know this notice until now. I'm one year outdated ;-)
But anyway, do you not think that we can support the PNG format through
kernel? It was designed thinking in opensource... [I believe]
And, the patent could be expired one year ago, but I think that the
kernel hackers use this format before this year: the kernel 2.4.23 has
the logo.gif, so I think that we can check easyly that the series 2.4.x
used (and uses) this format.
Regards,
Xan.
next reply other threads:[~2003-12-23 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 19:33 xan2 [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-23 19:41 Re: [License of kernel components] linux-2.x.y/Documentation/logo.GIF should be logo.PNG? xan2
2003-12-23 20:13 ` David Lang
2003-12-23 22:27 xan2
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=1a6d6d1a9664.1a96641a6d6d@ono.com \
--to=xan2@ono.com \
--cc=erik@harddisk-recovery.com \
--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