On Sat, Mar 5, 2011 at 11:05 AM, Ruben Laguna <ruben.laguna@xxxxxxxxx> wrote:
> Hi,
>
> I had a repo which was big 143MB because it contained a bunch of jar
> files. So I decided to remove those completely from the history.
>
> In short I used the git-large-blob [1] to find all the jars and used
> the git-remove-history script [2] which does the filter-branch thing,
> prune, etc.
>
> I did this on all branches (that I know of) and now I can see that the
> jars are gone because I can't find them with git-large-blob. Âand the
> repo size has dropped from 143Mb to 87Mb.
I just thought I'd mention that the git-remove-history script that you
mention does filter-branch on HEAD, and not using the --all parameter.
I thought --all was the best way to "catch all" branches in one go...
-- Tor Arvid
> My concern is that 87Mb is still really big taking into account he
> size of the project. Âin fact if I run "git diff-tree -r -p $commit
> |wc -c" for each commit and sum all I get 5.5Mb.
>
>
> I also ran the git-rev-size [3] script that I found in this mailing
> list and I only see that the size grows steadly from commit to commit
> up to 1482731 bytes. So again how come the .git directory is 87MB?
>
>
> So, Can anybody tell me if this repository size is "normal" for a
> project with 1.4MB source and 352 commits?
> Is there a better way to calculate the size (in bytes) of each commit?
>
> Is there any other thing I could do to reduce and audit Âthe repository size?
>
>
> Thanks in advance!
> RubÃn
>
> ---
> [1]Âhttp://stackoverflow.com/questions/298314/find-files-in-git-repo-over-x-megabytes-that-dont-exist-in-head
> [2]Âhttp://dound.com/2009/04/git-forever-remove-files-or-folders-from-history/
> [3] http://markmail.org/message/762zzg5zckbiq2i7
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at Âhttp://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html