On Wed, Mar 5, 2014 at 6:55 PM, Robert Dailey <rcdailey.li...@gmail.com> wrote: > What I'd like to do is somehow hunt down the largest commit (*not* > blob) in the entire history of the repository to hopefully find out > where huge directories have been checked in. > > I can't do a search for largest file (which most google results seem > to show to do) since the culprit is really thousands of unnecessary > files checked into a single subdirectory somewhere in history. > > Can anyone offer me some advice to help me reduce the size of my repo > further? Thanks.
If you are trying to see which commits changed the most files (and/or lines), you may find git log --oneline --shortstat helpful. A quick search through that output may help you decide where to dig further. Also, I'm sure someone else here probably has a better idea, but here's a quick hack I came up with to look at "commit sizes": mkdir tmp && for i in $(git rev-list --all); do git branch -f dummy $i && git bundle create tmp/$i.bundle dummy --not dummy^@; done Follow that up with a quick "ls -alrSh tmp/" and you can see the "size" of each commit. Hope that helps, Elijah -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
