git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Binary files

From
VSVolodymyr Sendetskyi <volodymyrse@devcom.com>
Date
Jul 20, 2017, 07:41 UTC
Message-ID
<CAFc9kS_xYVyPsW7qogDxLugxBb1p2vEFAoP=W9Rdnfqs6XtWKQ@mail.gmail.com>
In-Reply-To
<CAFc9kS8L-JJoJqKi7bB90qwKVW8gB=EFk9D8c=4YShqnamwa2w@mail.gmail.com>

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.

So the question is: why not implementing some feature, that would somehow handle this problem?

Of course, I don't know the internal git structure and the way of working + some nuances (likely about the snapshots at all and the way they are done), so handling this may be a great problem. But the easiest feature for me as an end user will be something like '.gitbinary', where I can list binary files, that would behave like on SVN, or even more optimal, if you can implement it. Maybe there will be a need for separate kinds of repositories, or even servers. But that would be a great change and a logical way of next git's evolution.

Next: Bryan Turner
Message 1 of 8 in “Re: Binary files”
  1. Volodymyr SendetskyiJul 20, 2017
  2. Bryan TurnerJul 20, 2017
  3. Konstantin KhomoutovJul 20, 2017
  4. Lars SchneiderJul 20, 2017
  5. Stefan BellerJul 20, 2017
  6. Igor DjordjevicJul 20, 2017
  7. Junio C HamanoJul 20, 2017
  8. Igor DjordjevicJul 21, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.