[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4740581C.6030206@keyaccess.nl>
Date: Sun, 18 Nov 2007 16:19:56 +0100
From: Rene Herman <rene.herman@...access.nl>
To: James Bottomley <James.Bottomley@...senPartnership.com>
CC: Pavel Machek <pavel@....cz>, Mark Lord <liml@....ca>,
Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
David Miller <davem@...emloft.net>, protasnb@...il.com,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
alsa-devel@...a-project.org, linux-ide@...r.kernel.org,
linux-pcmcia@...ts.infradead.org,
linux-input@...ey.karlin.mff.cuni.cz,
bugme-daemon@...zilla.kernel.org
Subject: Re: size of git repository (was Re: [BUG] New Kernel Bugs)
On 18-11-07 15:35, James Bottomley wrote:
>> clean-cg? But failure to run "git repack -a -d" every once in a while?
>
> Actually, the best command is
>
> git gc
>
> which does a repack (into a single pack file rather than an incremenal),
> and then removes all the objects now in the pack. If, like me, you work
> on temporary branches which you keep rebasing, you can add a --prune to
> gc which will erase all unreferenced objects as it packs (use this one
> with care. I usually never use it but run a git prune -n just to see
> what would be removed, and then run git prune separately if it looks OK).
Thanks for the comment. That managed to indeed shave a few extra bytes off
my already "repack -a -d" packed repo still.
Rene.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists