If this is day-to-day operation in your team, it might be that you are already feeling the pain from overly swollen Git repositories. Storing a snapshot of a virtual machine image, changing its state and storing the new state to a Git repository would grow the repository size approximately with the size of the respective snapshots. The growth directly affects the amount of data end users need to retrieve when they need to clone the repository. Because of the decentralized nature of Git, which means every developer has the full change history on his or her computer, changes in large binary files cause Git repositories to grow by the size of the file in question every time the file is changed and the change is committed. Storing large binary files in Git repositories seems to be a bottleneck for many Git users. I’ll post the original article in blockquote and my notes in green. ![]() This is a small update (1 year later) of a great article by Ilmari Kontulainen, first posted on.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |