From: Theodore Tso <tytso@mit.edu>
To: Jakub Narebski <jnareb@gmail.com>
Cc: "Björn Steinbrink" <B.Steinbrink@gmx.de>,
"Mikael Magnusson" <mikachu@gmail.com>,
"Bruce Stephens" <bruce.stephens@isode.com>,
git@vger.kernel.org
Subject: Re: "git gc" doesn't seem to remove loose objects any more
Date: Mon, 15 Dec 2008 14:38:37 -0500 [thread overview]
Message-ID: <20081215193837.GB11502@mit.edu> (raw)
In-Reply-To: <m3vdtlcqp6.fsf@localhost.localdomain>
On Mon, Dec 15, 2008 at 09:07:39AM -0800, Jakub Narebski wrote:
>
> There was an idea to have "git gc --prune" run "git prune"
> unconditionally, i.e. without grace period for dangling loose objects.
>
That doesn't help that much, since (temporarily) you still need all of
the disk space for the exploded, unpacked objects. As Brandon Casey
pointed out, the key is "git repack -a -d -l" vs "git repack -A -d
-l". If there is going to be a git-gc option, it would need to change
the options sent to git-repack. Or, I suppose the answer is to tell
people who run into this problem use a plumbing command, manually.
The question is how common is the use case of needing to gc a
repository like linux-next, I suppose.
- Ted
next prev parent reply other threads:[~2008-12-15 19:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 12:52 "git gc" doesn't seem to remove loose objects any more Bruce Stephens
2008-12-15 13:38 ` Mikael Magnusson
2008-12-15 14:08 ` Bruce Stephens
2008-12-15 14:08 ` Björn Steinbrink
2008-12-15 15:56 ` Theodore Tso
2008-12-15 16:12 ` Mark Brown
2008-12-15 16:59 ` Johan Herland
2008-12-15 16:59 ` Mikael Magnusson
2008-12-15 17:07 ` Jakub Narebski
2008-12-15 19:38 ` Theodore Tso [this message]
2008-12-15 17:11 ` Brandon Casey
2008-12-15 17:38 ` [PATCH] objects to be pruned immediately don't have to be loosened Nicolas Pitre
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=20081215193837.GB11502@mit.edu \
--to=tytso@mit.edu \
--cc=B.Steinbrink@gmx.de \
--cc=bruce.stephens@isode.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=mikachu@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.