git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Lucy Phipps <landfillbaby69@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Fwd: [PATCH] optimize PNGs with FileOptimizer 13.50.2431 (x86) and ZopfliPNG 1.0.2
Date: Thu, 24 Jan 2019 14:04:59 -0500	[thread overview]
Message-ID: <20190124190458.GA29828@sigill.intra.peff.net> (raw)
In-Reply-To: <CAGOd_F8A7Tfgb8cD1qvi2WDKYXLp=Zf_Yopb38gFpRQoj0tcdg@mail.gmail.com>

On Thu, Jan 24, 2019 at 06:34:29PM +0000, Lucy Phipps wrote:

> honestly i just like optimizing files. the test images still work but
> one of them is half the size as before. i don't know if it needs to be
> bigger. it doesn't make any actual difference

I'm not sure if we actually see any benefit to optimizing them, though.

Optimizing a file which is served to many clients makes sense. So these:

> > >  gitweb/static/git-favicon.png | Bin 115 -> 106 bytes
> > >  gitweb/static/git-logo.png    | Bin 207 -> 204 bytes

should be optimized (and largely already are, from the byte counts).

But these:

> > >  t/test-binary-1.png           | Bin 5660 -> 2603 bytes
> > >  t/test-binary-2.png           | Bin 275 -> 217 bytes

never go anywhere except developer's working trees. And since the
history is kept in Git, we keep the original version of the file, too.
So this is actually making git.git slightly _larger_, even though
checked-out file in the working tree is smaller.

I'm not sure that's worth the tradeoff.

-Peff

  reply	other threads:[~2019-01-24 19:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24 18:07 [PATCH] optimize PNGs with FileOptimizer 13.50.2431 (x86) and ZopfliPNG 1.0.2 Lucy Phipps
2019-01-24 18:10 ` Stefan Beller
     [not found]   ` <CAGOd_F8f=dURFE0H3qjMONy32nrSsXs5KHnogsosfwK92-KbYw@mail.gmail.com>
2019-01-24 18:34     ` Fwd: " Lucy Phipps
2019-01-24 19:04       ` Jeff King [this message]
2019-01-24 21:15         ` Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190124190458.GA29828@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=landfillbaby69@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).