From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "David Kågedal" <davidk@lysator.liu.se>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Lots of loose objects
Date: Wed, 10 Oct 2007 20:37:48 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0710102035420.4174@racer.site> (raw)
In-Reply-To: <87myuqwzp3.fsf@lysator.liu.se>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 778 bytes --]
Hi,
On Wed, 10 Oct 2007, David Kågedal wrote:
> I hade a tree that made git-gui complain that I had too many loose
> objects every time I started it (3072 to be precise). Letting git-gui
> compress it for me didn't help. Neither did git-gc, even with the
> --aggressive flag.
>
> I noticed that I had a lot of loose files in .git/objects, and
> suddenly I remembered that there was a command called "git
> prune". Finally I was able to get rid of those loose objects.
Probably git-gui should check again, after the compacting stage, how many
loose objects there are, and suggest to run git prune after a sufficiently
terrifying warning message ("Should I prune unreferenced objects? (DON'T
do this if you share objects between repositories!) Yes / No").
Ciao,
Dscho
prev parent reply other threads:[~2007-10-10 19:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 19:13 Lots of loose objects David Kågedal
2007-10-10 19:37 ` Johannes Schindelin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0710102035420.4174@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=davidk@lysator.liu.se \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).