git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Petko Manolov <petkan@nucleusys.com>
Cc: Wincent Colaiuta <win@wincent.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	David Symonds <dsymonds@gmail.com>,
	git@vger.kernel.org
Subject: Re: git and binary files
Date: Wed, 16 Jan 2008 10:09:41 -0800	[thread overview]
Message-ID: <7vprw1r6ai.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7vwsq9r6mf.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Wed, 16 Jan 2008 10:02:32 -0800")

Junio C Hamano <gitster@pobox.com> writes:

> Petko Manolov <petkan@nucleusys.com> writes:
>
>> On Wed, 16 Jan 2008, Wincent Colaiuta wrote:
>>
>>> If the exact contents of these large binaries *really* don't matter,
>>> as you say they don't, than why don't you just commit one and never
>>> touch it again?
>>
>> Unfortunately those binaries does change, although the process is slow
>> and not very frequent.  And this is why it pokes me in the eye - for
>> changing a few bytes i end up with much larger repository.
>
> For changing a few bytes you get with much larger repository?
> What happened to our packfiles?
>
> Is it possible for us to take a look at two versions of such a
> binary blob, one before the change and one after such a change
> that touches only a few bytes?

I replied before reading the rest of the thread.  Please ignore
me on this one.

  reply	other threads:[~2008-01-16 18:10 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 [this message]
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
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=7vprw1r6ai.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=dsymonds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=petkan@nucleusys.com \
    --cc=win@wincent.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).