Hi Michael, On Fri, 16 Mar 2018, Michael Haggerty wrote: > What makes a Git repository unwieldy to work with and host? It turns > out that the respository's on-disk size in gigabytes is only part of > the story. From our experience at GitHub, repositories cause problems > because of poor internal layout at least as often as because of their > overall size. For example, > > * blobs or trees that are too large > * large blobs that are modified frequently (e.g., database dumps) > * large trees that are modified frequently > * trees that expand to unreasonable size when checked out (e.g., "Git > bombs" [2]) > * too many tiny Git objects > * too many references > * other oddities, such as giant octopus merges, super long reference > names or file paths, huge commit messages, etc. > > `git-sizer` [1] is a new open-source tool that computes various > size-related statistics for a Git repository and points out those that > are likely to cause problems or inconvenience to its users. Thank you very much for sharing this tool. I packaged this as a MSYS2 package for use in Git for Windows' SDKs. You can install it via pacman -Sy mingw-w64-x86_64-git-sizer (obviously, if you are in a 32-bit SDK you want to replace x86_64 by i686) Note: I am simply re-bundling the binaries you post to the GitHub releases; The main purpose is to make it easier for users to include this in their custom installers. Second note: I briefly considered including this tool in Git for Windows, but it does increase the size of the installer by a full megabyte, and therefore I decided to keep it as SDK-only, optional package. Thanks! Dscho
