git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Kramer <benny.kra@googlemail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: Optimize git-favicon.png
Date: Mon, 10 Aug 2009 14:09:00 +0200	[thread overview]
Message-ID: <4A800DDC.8070301@googlemail.com> (raw)
In-Reply-To: <200908101357.49967.jnareb@gmail.com>

Reduce size of git-favicon.png using a combination of optipng and
pngout. From 164 bytes to 115 bytes (30% reduction). Also reduce
git-logo.png's size by one byte using advcomp.

Signed-off-by: Benjamin Kramer <benny.kra@googlemail.com>
---

Am 10.08.09 13:57, schrieb Jakub Narebski:
> 
> Can you optimize git-logo.png?  Smush.it wasn't able to do it, but
> perhaps different PNG optimization tool will reduce git-logo.png
> size...
> 

advcomp was able to shave one byte off git-logo.png. I don't know if
that's worth the effort.

 gitweb/git-favicon.png |  Bin 164 -> 115 bytes
 gitweb/git-logo.png    |  Bin 208 -> 207 bytes
 2 files changed, 0 insertions(+), 0 deletions(-)

diff --git a/gitweb/git-favicon.png b/gitweb/git-favicon.png
index de637c0608090162a6ce6b51d5f9bfe512cf8bcf..aae35a70e70351fe6dcb3e905e2e388cf0cb0ac3 100644
GIT binary patch
delta 85
zcmZ3&SUf?+pEJNG#Pt9J149GD|NsBH{?u>)*{Yr{jv*Y^lOtGJcy4sCvGS>LGzvuT
nGSco!%*slUXkjQ0+{(x>@rZKt$^5c~Kn)C@u6{1-oD!M<s|Fj6

delta 135
zcmXS3!Z<;to+rR3#Pt9J149GDe=s<ftM(tr<t*@sEM{Qf76xHPhFNnYfP!|OE{-7;
zjI0MY3OYE5upapO?DR{I1pyyR7cx(jY7y^{FfMCvb5IaiQM`NJfeQjFwttKJyJNq@
hveI=@x=fAo=hV3$-MIWu9%vGSr>mdKI;RB2CICA_GnfDX

diff --git a/gitweb/git-logo.png b/gitweb/git-logo.png
index 16ae8d5382de5ffe63b54139245143513a87446e..f4ede2e944868b9a08401dafeb2b944c7166fd0a 100644
GIT binary patch
delta 156
zcmV;N0Av5q0nY)D7zqdi0002!DLE{WAt!%wNkl<Zc-rli(F%Yd6hp6fOaK3mORa}A
z2z1~>otGhl0|P~i$)-spEt!DmG!4Oj(E`y{=&}QVPE<oMZAOGbjq8K~(J6VKR=YOW
zicn}%Cu(Zk>Vav`S8+sy%-3K4v`F-e93n=ACyP7?a2n|X$Q?(91Ro%p-ctYo000O{
KMNUMnLSTYNOFs$#

delta 157
zcmV;O0Al~o0nh=E7zqRe0000j+0-qOAt!%xNkl<ZD9>X^XCMShTo?)nDq>S%AOZ*t
zX+^A|p#d-qlVCO`QjxI%5!T^VWNd8AY-|jo3~(x91}ec~9kT%fQ=|y!00S5%RuR<U
zAeS59v<@{SaVdhCFu0Qn5xGT(!HuAzL?H$zL4rVq!9|H6Z~*|MJt4&s9Gd<B000R9
LNkvXXu0mjfVZ1Yp

-- 
1.6.4.67.gea5b1
 

      reply	other threads:[~2009-08-10 12:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10 11:00 [PATCH] gitweb: Optimize git-favicon.png Jakub Narebski
2009-08-10 11:39 ` Benjamin Kramer
2009-08-10 11:57   ` Jakub Narebski
2009-08-10 12:09     ` Benjamin Kramer [this message]

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=4A800DDC.8070301@googlemail.com \
    --to=benny.kra@googlemail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).