On Fri, May 31, 2013 at 09:49:57AM +0100, Alex Bennée wrote:
> On 31 May 2013 09:32, John Keeping <j...@keeping.me.uk> wrote:
> > Thomas is suggesting that you might have a tag that does not point at a
> > commit but instead points to a blob object.
> It's looking like I just have some very heavy commits. One data point
> I probably should have mentioned at the beginning is this was a
> converted CVS repo and I'm wondering if some of the artifacts that
> introduced has contributed to this.
You can try another for-each-ref invocation to see if that's the case:
eval $(git for-each-ref --format 'printf "%s %s\n" \
$(git cat-file -s %(objectname)) %(refname);') | sort -n
That will print the size of each object followed by the ref that points
to it, sorted by size.
> I'm running the GIT stable PPA:
> 09:38 ajb@sloy/x86_64 [work.git] >git --version
> git version 1.8.3
> Although I have also tested with the latest git.git maint. I'm happy
> to try master if it's likely to have changed.
master's still very close to 1.8.3 at the moment, so I don't think that
will make a difference.
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