From: walt <wa1ter@myrealbox.com>
To: git@vger.kernel.org
Subject: Re: Question about git-prune
Date: Sat, 30 Jun 2007 13:06:09 -0700 [thread overview]
Message-ID: <f66d3l$sa6$1@sea.gmane.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0706301900290.4438@racer.site>
Johannes Schindelin wrote:
> Hi,
>
> On Sat, 30 Jun 2007, walt wrote:
...
>> $git-prune
>> $git-fsck
>> dangling tree c642c018aa55d39fff061183f58062de9d8375ac
>> dangling commit e1341abc3759950e891822088cb0163b71b316b3
>> dangling commit 9f38e1ef7e7992ca490b9b419f52fb4d11efb0e4
>> dangling commit b82871b3c32faa8a317007f343fdf2d0ddc9954e
>
> Probably the objects were packed.
I also tried git-prune-packed, which also did nothing AFAICT.
> I do not understand why you use git-prune directly, to begin with. Why not
> use git-gc and be done with it?
It didn't exist when I started using git. I normally don't use
git-prune either, but in this case I was just scanning for problems
after switching from cg-update to git-pull.
git-gc did get rid of all the danglers even though git-prune didn't.
I'll do some investigating to find out why -- that should get me more
up to date with recent changes.
Thanks for your help.
next prev parent reply other threads:[~2007-06-30 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 16:29 Question about git-prune walt
2007-06-30 18:02 ` Johannes Schindelin
2007-06-30 20:06 ` walt [this message]
2007-06-30 20:12 ` Junio C Hamano
2007-06-30 20:18 ` Johannes Schindelin
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='f66d3l$sa6$1@sea.gmane.org' \
--to=wa1ter@myrealbox.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 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).