{"action":"closed","issue":{"url":"https://api.github.com/repos/sccn/labstreaminglayer/issues/80","repository_url":"https://api.github.com/repos/sccn/labstreaminglayer","labels_url":"https://api.github.com/repos/sccn/labstreaminglayer/issues/80/labels{/name}","comments_url":"https://api.github.com/repos/sccn/labstreaminglayer/issues/80/comments","events_url":"https://api.github.com/repos/sccn/labstreaminglayer/issues/80/events","html_url":"https://github.com/sccn/labstreaminglayer/issues/80","id":131374371,"number":80,"title":"git bloat","user":{"login":"cboulay","id":303797,"avatar_url":"https://avatars.githubusercontent.com/u/303797?v=3","gravatar_id":"","url":"https://api.github.com/users/cboulay","html_url":"https://github.com/cboulay","followers_url":"https://api.github.com/users/cboulay/followers","following_url":"https://api.github.com/users/cboulay/following{/other_user}","gists_url":"https://api.github.com/users/cboulay/gists{/gist_id}","starred_url":"https://api.github.com/users/cboulay/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cboulay/subscriptions","organizations_url":"https://api.github.com/users/cboulay/orgs","repos_url":"https://api.github.com/users/cboulay/repos","events_url":"https://api.github.com/users/cboulay/events{/privacy}","received_events_url":"https://api.github.com/users/cboulay/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-02-04T15:02:56Z","updated_at":"2016-02-04T23:08:57Z","closed_at":"2016-02-04T23:08:57Z","body":"I can't pinpoint when it started, but I noticed recently that cloning labstreaminglayer takes a lot longer than it used to (but not as long as google code days). The clone that I completed just a minute ago downloaded 265.89 MiB.\r\n\r\n```\r\ngit clone https://github.com/sccn/labstreaminglayer.git\r\nCloning into 'labstreaminglayer'...\r\nremote: Counting objects: 44937, done.\r\nremote: Compressing objects: 100% (21/21), done.\r\nremote: Total 44937 (delta 4), reused 0 (delta 0), pack-reused 44913\r\nReceiving objects: 100% (44937/44937), 265.89 MiB | 580.00 KiB/s, done.\r\nResolving deltas: 100% (23887/23887), done.\r\nChecking connectivity... done.\r\n```\r\n\r\n `du -hs <dirname>` gives me 401M for `labstreaminglayer`, within which we get 59M for `Apps`, 74M for `LSL`, and 268M for `.git`. (this is all before I do a get_deps)\r\n\r\nMy guess is that some binaries are being tracked that previously were not.\r\n\r\nI followed some steps [found on the web](http://blog.jessitron.com/2013/08/finding-and-removing-large-files-in-git.html) to get a list of large-ish files in the history. See attached. There are a bunch of tools on the web for dealing with this problem. If you decide to cleanup the repo, downstream repos will no longer be compatible so they will have to do a new fork or a new clone. While this is not desirable, it's certainly better to do it sooner than later.\r\n[large_files.txt](https://github.com/sccn/labstreaminglayer/files/117624/large_files.txt)\r\n"}}