From: Paulo Marques <pmarques@grupopie.com>
To: xan2@ono.com
Cc: andersen@codepoet.org, Gene Heskett <gene.heskett@verizon.net>,
linux-kernel@vger.kernel.org
Subject: Re: [License of kernel components] linux-2.x.y/Documentation/logo.GIF should be logo.PNG?
Date: Fri, 26 Dec 2003 17:48:27 +0000 [thread overview]
Message-ID: <3FEC746B.6060608@grupopie.com> (raw)
In-Reply-To: 1b93041b9c9f.1b9c9f1b9304@ono.com
xan2@ono.com wrote:
> ...
>
> For this reason, because in many countries the patent is not expired and
> that kernel is not _only_ for people of U.S., I think that we have to
> change to PNG format rather than gif.
>
> I vote for pass to PNG format as fast as we can.
You're not *listening*: only the encoding of the gif is encumbered by patents.
The "decoding" of the gif is *not*.
So only the original author of the gif had to worry about using a software that
had a license to generate GIF's (like photoshop, etc.). To use/decode the GIF
there are no restrictions. AFAIK, there are absolutely no patent infrigments in
distributing the logo.gif file.
Now that I've said this, I must say that I would also prefer a completely
open-source format like PNG to be used :)
--
Paulo Marques - www.grupopie.com
"In a world without walls and fences who needs windows and gates?"
next prev parent reply other threads:[~2003-12-26 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 22:27 Re: [License of kernel components] linux-2.x.y/Documentation/logo.GIF should be logo.PNG? xan2
2003-12-26 17:48 ` Paulo Marques [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-23 15:20 xan2
2003-12-23 16:16 ` Erik Mouw
2003-12-23 17:07 ` Gene Heskett
2003-12-23 19:38 ` Erik Andersen
2003-12-23 20:45 ` Ian Hastie
2003-12-23 21:43 ` Edesio Costa e Silva
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=3FEC746B.6060608@grupopie.com \
--to=pmarques@grupopie.com \
--cc=andersen@codepoet.org \
--cc=gene.heskett@verizon.net \
--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.