Re: git and binary files

From: Jakub Narebski <jnareb@gmail.com>
Date: Jan 16, 2008, 14:20 UTC
Message-ID: <200801161520.44668.jnareb@gmail.com>
In-Reply-To: <alpine.DEB.1.00.0801161600030.5260@bender.nucleusys.com>

Petko Manolov wrote:

Show 7 quoted lines

> On Wed, 16 Jan 2008, Jakub Narebski wrote:
> 
> > You can always tag a blob (like junio-gpg-pub tag in git.git repository),
> > but it wouldn't be in a working directory. But it would get distributed
> > on clone.
> 
> Hm, how does it work?

You use git-hash-object to put file (-t blob) into the object database. It would return sha1 of added object. Use git-tag to create tag to blob (use returned sha1 for head). You can get file (to stdout) with "git cat-file blob tagname^{blob}".

The file would be in object database, but not in working directory by default.

Show 7 quoted lines

> > BTW. if those large binary files doesn't differ much between version, 
> > they should get well compressed even if you would store them normally, 
> > all revisions.
> 
> Unfortunately this is not the case.  These binary blobs are already 
> compressed and/or encrypted and adding even a few bytes ends up storing 
> new version in full size.

Can't you store them uncompressed?

-- 
Jakub Narebski
Poland