From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: git packing leaves unpacked files
Date: Tue, 26 Sep 2006 20:10:25 +0200 [thread overview]
Message-ID: <efbqeb$guv$1@sea.gmane.org> (raw)
In-Reply-To: 45196BC8.8060608@shadowen.org
Andy Whitcroft wrote:
> I was just looking at my kernel repository and noticed that even after a
> git repack -a -d I have some loose files. A quick look at repack
> doesn't seem to explain why some are either not packed or are kept unpacked.
>
> Is this something I should be expecting?
Try git-fsck-objects. Perhaps those loose files are the ones which will
be pruned.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-09-26 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 18:04 git packing leaves unpacked files Andy Whitcroft
2006-09-26 18:10 ` Jakub Narebski [this message]
2006-09-26 18:28 ` Linus Torvalds
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='efbqeb$guv$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--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 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.