From: Igor Djordjevic <igor.d.djordjevic@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Volodymyr Sendetskyi <volodymyrse@devcom.com>, git@vger.kernel.org
Subject: Re: Binary files
Date: Fri, 21 Jul 2017 19:46:51 +0200 [thread overview]
Message-ID: <0d2dcfc0-81e0-ff16-3d21-7148978f8100@gmail.com> (raw)
In-Reply-To: <xmqqo9sekfjm.fsf@gitster.mtv.corp.google.com>
On 20/07/2017 22:40, Junio C Hamano wrote:
> Igor Djordjevic <igor.d.djordjevic@gmail.com> writes:
>> On 20/07/2017 09:41, Volodymyr Sendetskyi wrote:
>>> It is known, that git handles badly storing binary files in its
>>> repositories at all.
>>> This is especially about large files: even without any changes to
>>> these files, their copies are snapshotted on each commit. So even
>>> repositories with a small amount of code can grove very fast in size
>>> if they contain some great binary files. Alongside this, the SVN is
>>> much better about that, because it make changes to the server version
>>> of file only if some changes were done.
>>
>> You already got some proposals on what you could try for making large
>> binary files handling easier, but I just wanted to comment on this
>> part of your message, as it doesn`t seem to be correct.
>
> All correct. Thanks.
No problem, thanks for confirmation, being relatively new around it`s
appreciated, at least knowing that I got it correct myself :)
prev parent reply other threads:[~2017-07-21 17:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFc9kS8L-JJoJqKi7bB90qwKVW8gB=EFk9D8c=4YShqnamwa2w@mail.gmail.com>
2017-07-20 7:41 ` Binary files Volodymyr Sendetskyi
2017-07-20 7:58 ` Bryan Turner
2017-07-20 8:01 ` Konstantin Khomoutov
2017-07-20 8:32 ` Lars Schneider
2017-07-20 17:22 ` Stefan Beller
2017-07-20 18:49 ` Igor Djordjevic
2017-07-20 20:40 ` Junio C Hamano
2017-07-21 17:46 ` Igor Djordjevic [this message]
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=0d2dcfc0-81e0-ff16-3d21-7148978f8100@gmail.com \
--to=igor.d.djordjevic@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=volodymyrse@devcom.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).