On Wed, 16 Jan 2008, Jakub Narebski wrote:
Petko Manolov wrote:
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}".
Sounds like i'll have to play with the above. Thanks for the tip.
The file would be in object database, but not in working directory
by default.
Not a big problem.
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?
Not really, but i can convert them into ascii format and store only the
delta. This will admittedly increase the initial size of the repository,
but hopefully not by much.
Petko
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
