From: "Dirk Süsserott" <newsletter@dirk.my1.cc>
To: Git Mailing List <git@vger.kernel.org>
Subject: How to prevent Git from compressing certain files?
Date: Wed, 22 Jul 2009 21:49:31 +0200 [thread overview]
Message-ID: <4A676D4B.7040004@dirk.my1.cc> (raw)
Hi,
I'm (ab)using Git to store my media files, i.e. digicam pictures (*.jpg)
and the like. This way I can e.g. comment a series of pictures without
installing and learning a special purpose "Photo Archiving" tool. Gitk
shows the roadmap!
Somewhere I read that Git isn't supposed to efficiently handle binary
files. Of course, I don't want to merge my files, just store them with
their history and git-push them to some "safe place".
I figured that pushing and git gc'ing both try to compress those files
(or differences) really hard. Works great for "regular" files, but is
pointless with jpegs.
Question: Is there a way to prevent Git from trying to compress certain
files based on their extension?
-- Dirk
next reply other threads:[~2009-07-22 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 19:49 Dirk Süsserott [this message]
2009-07-22 20:44 ` How to prevent Git from compressing certain files? Jakub Narebski
2009-07-22 20:46 ` Jakub Narebski
2009-07-23 10:12 ` Jeff King
2009-07-23 18:51 ` Dirk Süsserott
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=4A676D4B.7040004@dirk.my1.cc \
--to=newsletter@dirk.my1.cc \
--cc=git@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;
as well as URLs for NNTP newsgroup(s).