From: <xan2@ono.com>
To: gene.heskett@verizon.net
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:41:24 +0100 [thread overview]
Message-ID: <19af2619c848.19c84819af26@ono.com> (raw)
Gene Heskett <gene.heskett@verizon.net> wrote (23th, 2003 6:07 pm)
>>Re: [License of kernel components] linux-2.x.y/Documentation/logo.GIF
should be logo.PNG?
>
> On Tuesday 23 December 2003 10:20, xan2@ono.com wrote:
> >Hi,
> >
> >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]).
>
> I don't think GIF was ever "proprietary", but the l-z-w compression
> used was patented. The patent expired earlier this year. So gif
> is
> back.
Sorry. I'm outdated. ;-)
But, why not support a opensource format like PNG?
And yes, now is expired but i think that we (the kernel users) used the
gif format one year ago (I think that it's trivial to check that 2.4.x
series used gif format. So they (patent registers of LZW) might demand
the money that we did not pay to their.
Regards,
Xan.
next reply other threads:[~2003-12-23 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 19:41 xan2 [this message]
2003-12-23 20:13 ` Re: [License of kernel components] linux-2.x.y/Documentation/logo.GIF should be logo.PNG? David Lang
-- strict thread matches above, loose matches on Subject: below --
2003-12-23 22:27 xan2
2003-12-23 19:33 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=19af2619c848.19c84819af26@ono.com \
--to=xan2@ono.com \
--cc=gene.heskett@verizon.net \
--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