git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Petko Manolov <petkan@nucleusys.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: git and binary files
Date: Wed, 16 Jan 2008 17:34:13 +0100	[thread overview]
Message-ID: <200801161734.13481.jnareb@gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0801161640010.5260@bender.nucleusys.com>

On Wed, 16 January 2008, Petko Manolov wrote:
> 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.

Please read carefully section about retagging / changing a tag
in git-tag(1) manpage; you should take care about propagating change
if you ever change the binary blob.

Nothe that I haven't used the technique described.

-- 
Jakub Narebski
Poland

  parent reply	other threads:[~2008-01-16 16:34 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16 10:34 git and binary files Petko Manolov
2008-01-16 10:54 ` David Symonds
2008-01-16 13:21   ` Petko Manolov
2008-01-16 13:42     ` Johannes Schindelin
2008-01-16 13:58       ` Petko Manolov
2008-01-16 14:07         ` Johannes Schindelin
2008-01-16 14:21           ` Petko Manolov
2008-01-16 14:34         ` Wincent Colaiuta
2008-01-16 14:45           ` Petko Manolov
2008-01-16 18:02             ` Junio C Hamano
2008-01-16 18:09               ` Junio C Hamano
2008-01-16 11:54 ` Johannes Schindelin
2008-01-16 13:39   ` Petko Manolov
2008-01-16 13:53     ` Jakub Narebski
2008-01-16 14:04       ` Petko Manolov
2008-01-16 14:20         ` Jakub Narebski
2008-01-16 14:43           ` Petko Manolov
2008-01-16 15:01             ` Nicolas Pitre
2008-01-16 15:18               ` Petko Manolov
2008-01-16 15:58                 ` Nicolas Pitre
2008-01-16 16:06                   ` Petko Manolov
2008-01-16 16:09               ` Petko Manolov
2008-01-16 16:34             ` Jakub Narebski [this message]
2008-01-16 16:41             ` Florian Weimer
2008-01-16 13:54     ` Jeff King
2008-01-16 14:14       ` Petko Manolov
2008-01-16 14:18         ` Jeff King
2008-01-16 14:25           ` Petko Manolov
2008-01-16 14:32             ` Jeff King
2008-01-16 14:39               ` Petko Manolov
2008-01-16 15:05                 ` Rogan Dawes
2008-01-18  6:52                 ` David Brown
  -- strict thread matches above, loose matches on Subject: below --
2010-07-28 14:17 Jan Dittmer
2010-07-28 14:29 ` Matthieu Moy
2010-07-28 20:17   ` Avery Pennarun
2011-04-28 15:11 Git and Binary Files ryanzec
2011-04-28 15:26 ` Peter Jönsson P

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=200801161734.13481.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=petkan@nucleusys.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).